The find-prefix infrastructure was required in a pkgviews world where
packages installed from pkgsrc could have different installation
prefixes, and this was a way for a dependency prefix to be determined.
Now that pkgviews has been removed there is no longer any need for the
overhead of this infrastructure. Instead we use BUILDLINK_PREFIX.pkg
for dependencies pulled in via buildlink, or LOCALBASE/PREFIX where the
dependency is coming from pkgsrc.
Provides a reasonable performance win due to the reduction of `pkg_info
-qp` calls, some of which were redundant anyway as they were duplicating
the same information provided by BUILDLINK_PREFIX.pkg.
Problems found with existing distfiles:
distfiles/javascript-2.1b1.el
distfiles/yEd-3.14.2.zip
No changes made to the javascript-mode or yEd distinfo files.
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
o Update packages
o Use DESTDIR features for installing, getting rid of the need to be
root and gaining the ability to patch elisp files in the process.
o Add a mechanism to re-byte-compile the patched elisp files, and
patches to deal with non-utf-8 XEmacsen.
o Grab maintainership
Tested with both 21.4 and 21.5 packages.
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.
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.
against the xemacs{,-current} packages.
While here, listen to pkglint some.
From the edit-utils changelog:
2008-06-09 Aidan Kehoe <kehoea@parhasard.net>
* fast-lock.el (fast-lock-cache-directories):
Remove the directory the file is in, to avoid running code from
arbitrary other users. Update the docstring to motivate this.
Also, mark it as a risky local variable to prevent it being
evaluated in file local variable sections.
Thank you Ulrich Müller, thank you Hans de Graaff.
XXX The package versions this pkg installs are positively behind the bend.
magic of buildlink here, but in the meantime, there's not much point in
having an xemacs-nox11 without allowing it to install the packages.
(Actually, should xemacs-nox11 become xemacs with PKG_OPTIONS.xemacs without
`x11'?
Which way are we going with these things?)
each directory per version.
Before:
% ls -rt /usr/pkgsrc/distfiles/xemacs-packages*/apel*
/usr/pkgsrc/distfiles/xemacs-packages-1.9/apel-1.25-pkg.tar.gz
/usr/pkgsrc/distfiles/xemacs-packages-1.10/apel-1.26-pkg.tar.gz
/usr/pkgsrc/distfiles/xemacs-packages-1.12/apel-1.26-pkg.tar.gz
/usr/pkgsrc/distfiles/xemacs-packages-1.11/apel-1.26-pkg.tar.gz
After:
% ls -rt /usr/pkgsrc/distfiles/xemacs-packages*/apel*
/usr/pkgsrc/distfiles/xemacs-packages/apel-1.25-pkg.tar.gz
/usr/pkgsrc/distfiles/xemacs-packages/apel-1.26-pkg.tar.gz
Pointed out by Robert Elz, PR22085.