(to deal with a common shared Cygnus configure)
Move MODGNU_configure definition to gnu.port.mk. Should have done that on
creation.
Typo in brad's hack (to be superseded shortly anyways)
This can speed up some iterations, as a dependency won't be checked more
than once. This also allows for make extract NO_DEPENDS=Yes, then later
to have the dependencies pulled in at configure stage (even though this
might not work all the time, as some dependencies may be needed earlier
but then you'll certainly notice).
- allow for several libraries, separated by commas.
- try to heed dependency most closely. Notably, make sure the spec
stops at a sensible place. This may break some ill-formed dependencies.
Turns out this can be done based on target, directly, instead of
relying on /nonexistent.
One step closer to turning TRUST_PACKAGES=Yes on by default...
of sourceware.cygnus.com (also known as sources.redhat.com))
o Modify bzip2 and gsl ports to use this new master_site (gnats
remains to be fixed: no reply from maintainer)
o Bump NEED_VERSION on those ports
maintainers of the ports ok: brad@, rohee@
This is work-in-progress. Supplemental hooks will be added when they
become necessary.
The goal is to permit separate subsystems to tweak the package building
process slightly. This should help e.g., python or qt2, for instance.
Documentation will come when it's tested more thoroughly...
work-* is too long, because we want to include the PKGNAME in the dir name
(so that PKGNAME changes are less likely to work with old work directories)
Change the way clean works, so that you can say
make clean='dist depends packages' and have it do what you think it should
do.
Common fragment to _create_wrkobjdir.
Put some info into PACKAGING (name of subpackage being built)
Since those are mostly infrastructure-side, making SUBPACKAGE transparent
only adds to the confusion, so don't interpolate SUBPACKAGE into
FULLPKGNAME, hiding it into _FULLPKGNAME, but rather let FULLPKGNAME
tag the main package, and use FULLPKGNAME-foo for subpackage -foo.
This will simplify some other stuff...
- define _FULLPKGNAME* and _PKGFILE*. Use _PKGFILE* as package cookie
instead of package_done.
- use ${PKG_DBDIR}/${_FULLPKGNAME${SUBPACKAGE}/+CONTENTS as install cookie.
- BIN_PACKAGES variable. If set to yes, remove coupling between
PACKAGE_COOKIE and dependencies, so that binary packages exist
independently of working directories.
- mark packages as precious.
- change all refs to PKGFILE to _PKGFILE${SUBPACKAGE}.
- add bulk-packages target.
Note that BIN_PACKAGES and TRUST_PACKAGES are off by default.
This interface is likely to change. The name bulk-packages will probably
change as well.
We will probably get rid of the old PKGFILE/FULLPKGNAME (taking SUBPACKAGE
into account) and use the new PKGFILE/FULLPKGNAME
PKGFILE-foo/FULLPKGNAME-foo instead (with explicit subpackage information).
This is less confusing and simpler.
