Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
Noted by Wen Heping.
|
|
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
|
|
|
|
|
|
MASTER_SITE_RUBYGEMS and MASTER_SITE_HASKELL_HACKAGE.
|
|
|
|
|
|
In pkgsrc emul framework, "sunos" is SunOS 4.x, and "solaris" is SunOS 5.x.
|
|
|
|
Just define PKGNAME and use it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Replace PYTHON_PATCH_SCRIPTS with REPLACE_PYTHON.
|
|
Version->4.135
|
|
Upstream doesn't talk about it any longer, and python-3.3 is a drop-in
replacement.
Ok bsiegert, prlw1, rodent
|
|
Allow https in one more place.
Bump version.
|
|
perl modules. (fix USE_TOOLS to have perl:run instead of just perl)
|
|
- Improved allowed filenames for patches
- Added license for pkglint itself
- Cleaned up Makefile and TODO
|
|
|
|
page installation.
|
|
|
|
helps to see which source line belongs to which warning.
- PKGSRCTOP is a known variable. It is used only in the top-level
Makefile.
- Arbitrary tool names may be added to TOOLS_NOOP.
- In the top-level Makefile, the alphabetic order of the SUBDIRs
may have a single exception.
|
|
- improved wording of some warnings
- added explanations to some common warnings
|
|
Bump version.
|
|
|
|
|
|
|
|
|
|
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
|
|
"u" means "use at runtime", i.e. the variable may not be available
during preprocessing.
"t" wasn't used at all (my error -- wiz)
Bump version.
|
|
|
|
* explain when desktop-file-utils is required.
* error missing {hicolor,gnome}-icon-theme.
|
|
* In test, match the "make makesum" warning more loosely.
* In test, find packages to run against in $PKGSRCDIR explicitly.
* Bump version.
This is the last commit in a set developed for my "Rehabilitating
pkglint" talk at pkgsrcCon 2013.
Reviewed-at-pkgsrcCon-and-approved-during-the-freeze-by: wiz
|
|
This regex almost certainly didn't intend to match an occurrence
of "ARRAY" in PkgLint::Line, but it did match.
|
|
Leave the silly self-grep in place, adjusting to also match the
lines that initialize the dispatch table. The underlying code is
better and the tests still pass. (No functional change intended.)
|
|
pkglint greps itself (really) to generate this list of types. Test
exhaustively for all types in the list today, so that the tested
code can become more civilized tomorrow. Adds a test-time dependency
on Test::Deep for cmp_bag().
|
|
This is more correct and more polite. For instance, pkglint.t no
longer needs to declare a package of its own just for tests.
|
|
In the configure stage, tell pkglint to find *.map in ${FILESDIR}.
That lets tests run even when pkglint isn't installed (which means
it also makes the tests less wrong when pkglint is installed!).
In the install stage, tell pkglint to find *.map under ${PREFIX},
as before (no functional change to the installed package).
Specify USE_TOOLS=perl to quell pkglint. :-)
|
|
|
|
These bits of non-main functionality are distracting to the casual
reader, and also to your intrepid refactorer. Since we recently
added some characterization tests that run the pkglint executable
against real packages, we can safely extract bits of code to separate
files and prove nothing broke in the move.
Instead of installing the new Perl modules where pkglint can find
them at runtime, I've added a build step to inline them right back
where they used to be (same order and everything). This is a little
annoying, but less annoying than suddenly needing to deal with Perl
runtime paths just for these few tiny modules. Also, loading modules
at runtime would affect pkglint's performance, and I don't yet have
performance tests to prove that this would be fine (or not), so I
can't safely do it.
No functional change intended.
|
|
|