| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
it again.
|
|
lock, which I think is what was originally intended.
* Avoid creating ${WRKDIR}/.depends when running the bootstrap-depends
target, which is run as part of running the fetch target. We still
create the .depends file later when we need it.
XXX Note that there are still problems when locking occurs because locks
XXX are created in ${WRKDIR}, so running "bootstrap-depends" as a source
XXX for "fetch" will still cause the work directory to be created and
XXX populated with files. This probably needs to be solved by using a
XXX different location for the lockfile, e.g. ${TMPDIR}, for the
XXX bootstrap-depends step.
|
|
relevant code that loads the configuration.
|
|
make happy on my older (netbsd-2) NetBSD box.
|
|
in WRKDIR.
|
|
+BUILD_INFO we must ensure that we only test valid lines from PLIST and
not lines like "@unexec /bin/rmdir..." where "/bin/rmdir" is not a part
of the resulting package.
To achieve this, a stripped version of PLIST, called _PLIST_NOKEYWORDS,
is introduced.
|
|
|
|
passed to the configure or build phases. This variable holds a slightly
different value depending on whether GNU_CONFIGURE is defined or not --
in the former case, the value is tuned for passing the GNU configure
script.
Automatically pass TOOLS_ENV to GNU configure scripts, so there is no
user-visible change.
|
|
change within the .for loop.
|
|
Raised on tech-pkg 2007-05-16, no objections.
|
|
|
|
|
|
depends.mk. The quoting of arrays passed down is almost impossible
to get right. For example, PKG_BUILD_OPTION.* variables can contain
multiple space separated entries but have to be quoted twice.
The original commit exposed two separate issues:
- too many variables are passed down via MAKEFLAGS, including the above
mentioned PKG_BUILD_OPTIONs.
- x11/gtk2 used an invalid variable name that can't be assigned
correctly via make command line.
This is supposed to fix PR 36387.
|
|
|
|
account that CVS usually leaves empty directories around. This fixes the
bootstrapping after a "cvs update" without the -P option. The error
message leading to it was:
===> running: (cd /home/p/src/devel/bmake && /home/p/pkg/bin/bmake -s
-DPKG_PRESERVE MAKECONF=/home/p/work/mk.conf.example
WRKOBJDIR=/home/p/work/pkgsrc bootstrap-register)
ERROR: [resolve-dependencies] A package matching ``digest>=20010302'' should
ERROR: be installed, but one cannot be found. Perhaps there is a
ERROR: stale work directory for ../../pkgtools/digest?
|
|
top-level directory of pkgsrc.
|
|
between them. Up to now, "bmake help topic=configure" looked rather
compressed.
|
|
From Zafer Aydogan.
|
|
is reported.
Fixed the output by not nestedly redirecting the output of "bmake debug".
|
|
|
|
Noticed by rillig@
|
|
So ensure that we don't pollute the environment at all and push down
the arguments for install-dependencies via the command line.
Thanks to seb@ for the problem report and test.
|
|
dependency installation, it occured to me that "make depends" doesn't
run the bootstrap-depends target correctly anymore. A deeper analysis
didn't show why it happened to work as it is only requested explicitly
by fetch. It wasn't an issue as all bootstrap dependencies were checked
again before, but fix this correctly by listening as dependency of
depends as well.
|
|
|
|
time for bootstrap-dependencies, only really only look at the bootstrap
dependencies. Skip them in the second run.
Confusion reported by xtraeme@
|
|
trace the dependency information. This is computed and stored in
.depends directly now before anything else is done. The output is locked
and the locking is supposed to work before the bootstrap-depends are
installed.
Add a new hook for flavors after all dependencies are added and before
the depends-cookie is created. Use this to compute which package is used
to fulfill each dependency and store it in .rdepends. Adjust
register-dependencies and some other places to use this information
directly instead of recomputing it all the time.
The code to list all dependencies and to recursively install missing
ones is moved to a separate shell script. This makes it easier to
understand what is going on and extend them later.
Change the calling of pkg_create to prepend the dependencies directly to
the passed-in PLIST and not via -P and -T. This is in preperation of
changing the way they are stored in the packages.
Discussed with, recieved minor disagreement about install-dependencies,
but otherwise OKed by jlam.
|
|
# pkglint -Wall
FATAL: ../../mk/fetch/sites.mk:56: Unknown line type.
|
|
|
|
packages that should not be built on non-NetBSD systems.
|
|
|
|
|
|
|
|
|
|
line is no longer printed by default. To get that behavior back, you can
set the variable WRAPPER_DEBUG to "yes".
This avoids some noise during the build. The old behavior was mostly
useful on Solaris and IRIX, where a -std=c99 or -c99 option had been
added to the compiler's arguments by the wrapper. This caused
diagnostics that were hard to understand, since the user did not specify
these flags and there was no sign that they had been added.
|
|
|
|
from /usr/kerberos and /dev/random in sandbox. On FreeBSD, use
devfs to populate /dev in sandbox.
From Sergey Svishchev.
|
|
|
|
|
|
|
|
pbulk-index-item prints a number of variables used by the parallel bulk
build code during either the build, the report or the upload phase.
pbulk-index checks whether multiple versions of the current package
could be build (e.g. because multiple Python versions are supported) and
uses pbulk-index-item for each possible combination.
Thanks to David Laight for explaining the different between using :[#]
in the body of a make target and in a clause of an .if.
Powered-by: Google SoC 2007.
|
|
|
|
operator. An example version is 1.5.24(0.156/4/2).
|
|
|
|
|
|
* allow "-" (stdin)
* allow other than regurar file (should fix PR 36257).
* if doesn't exist, try to append extension ".po" and ".pot".
|
|
package is returned rather than querying the source package. First, this
is more correct, and second, it greatly speeds up pkgsrc, especially
when many packages are already installed.
|
|
|
|
--version-script works are few enough to warrant fixing each one of them
instead. Silenty dropping the flag makes it impossible to detect whether or
not --version-script is supported. Pointed out by joerg@
|
|
the variables CONFIGURE_ARGS, _DISTFILES, _PATCHFILES and
_PLIST_IGNORE_FILES to the +BUILD_INFO file.
Fixes PR 36228.
|
|
|
