| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
obvious 2) we're in freeze, so restore to working as quickly as
possible.
|
|
tar up, instead of PKGBASE.
This enables modifying that file to have a package that isn't
automatically found be the replace target, e.g., "echo libglade2-2.6.2
> work/.replace_oldname" after make replace fails to find a package to
tar up when doing make replace in libglade.
|
|
dependency (bootstrap, build, full) is printed.
When building a package that pulls in the basic tools as dependencies,
it is good to know whether these are build or full dependencies, so the
additional information is useful.
|
|
|
|
|
|
|
|
- check-perms.mk was not DESTDIR aware, prefix files before passing it
to the directory extraction
- PKG_FILELIST_CMD was calling pkg_info, which is fine for normal
installation, but fails of course for DESTDIR. Just drop the @ lines
from ${_DEPENDS_PLIST} and use that.
- To make he former work, ensure that _flavor-generate-metadata is part
of _INSTALL_ALL_TARGETS. It was normally a dependency of
_flavor-register, but that is skipped for DESTDIR.
- Remove ${_DEPENDS_PLIST} when running install-clean.
|
|
instead only remove the files generated by _flavor-generate-metadata.
This should preserve the +INSTALL and +DEINSTALL scripts (which are
created during the "build" phase") across a "make update" or a "make
deinstall".
|
|
Use $$newname consistently rather than $PKGBASE and $PKGNAME.
Rationalize @ with STEP_MSG.
Ensure ${RUN} is used once, and all commands are included.
|
|
- Replaced ${_PKG_SILENT}${_PKG_DEBUG} with ${RUN},
- Moved the code to load oldname into a macro.
|
|
|
|
than in work/.pkgdb, so as not to lose them in install-clean.
Because of this, put them back explicitly.
(Fixes 'make replace loses +REQUIRED_BY', and also the unreported
'make replace loses +INSTALLED_INFO'.)
|
|
names to indicate that they are purely private to flavor/pkg.
|
|
contains files that are generated during the "install" phase. This
should fix the problem where PLIST modifications were ignored if the
PLIST was modified between a "make deinstall" and a "make reinstall".
|
|
to locate the +CONTENTS file for a "blank" package.
Why are there blank lines at all in +REQUIRED_BY?
|
|
|
|
been replaced which might have had an ABI change. In practice, a
package is considered to maybe have had an ABI change if the version
changes. Introduce a new tag unsafe_depends_strict, which is
unconditionally set on depending packages whenever make replace is
done.
This will cut down considerably on the amount of rebuilding required
with pkg_rolling-replace, while still guaranteing that packages are
rebuilt if there was an ABI change in a dependency.
|
|
+INSTALLED_INFO is present, to avoid complaint from pkg_admin (see
pkg/36741). Separate tag removal into a separate target, and use
STEP_MSG and _PKG_DEBUG properly.
|
|
fixing up the required-by file. The invariant on unsafe_depends (on
which pkg_rolling-replace depends) is once again maintained, but now
cleanly, rather than assuming that all tags are cleared.
(proposed on tech-pkg with no objections, and concurrence from tnn@)
|
|
installed. Idea from one of joerg@'s patches.
|
|
require pkg_install-20070802 for using it. It is now considered
to work correctly and ready for general consumption.
|
|
before replacing it, and restore it when the new package is installed.
This saves any state information that should be carried over to the
new package, e.g. automatic=yes.
XXX Still need to do the same when "un-replacing".
|
|
- USE_CROSS_COMPILATION activates it, CROSS_DESTDIR specifies root of
the target filesystem
- derive _CROSS_DESTDIR from CROSS_DESTDIR or MAKEOBJDIR
- buildlink3.mk prefixes the files to symlink with _CROSS_DESTDIR
- compiler/gcc.mk knows about the target prefix (e.g. i386--netbsdelf)
- PKG_DBDIR is prefixed with _CROSS_DESTDIR
- package-install and bin-install are not called with su
- install and strip are redirected to the tool version
- links for the target specific ar, as, ld, nm, objdump, ranlib and
strip are added
- compiler wrapper detect if linking is requested or not
- special command sinks for CPP and CC/CXX add the cross-compile magic:
- modify include dirs to get the target /usr/include
- modify linker dirs and runpath to use target /usr/lib at link time,
but keep correct rpath entries
Supported-by: Google SoC 2007
Basic tests by he@ on Sparc. Review from jlam@.
|
|
audit-packages.
|
|
that either.
|
|
the purpose of print-PLIST in plist/common-dirs.mtree.
Discussed with wiz@, no objections on tech-pkg@.
|
|
cannot ask for a password and fails. Patch provided by OBATA Akio in
http://mail-index.netbsd.org/pkgsrc-users/2007/04/23/0001.html
|
|
patterns. Otherwise the upper bound would silently get dropped.
|
|
appropriately again based on the value of _BOOTSTRAP_VERBOSE. This
code was lost in revision 1.27.
This should again suppress the output during "mirror-distfiles" in the
case where the bootstrap dependency is already installed.
|
|
(This is needed for changing the "set -e" to "set -eu" in the ${RUN} macro.)
|
|
because /bin/sh on Solaris doesn't understand this syntax and bmake
uses this ancient shell.
bmake should really be built with /bin/ksh or /usr/xpg4/bin/sh as the
default shell.
|
|
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.
|
|
+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.
|
|
|
|
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.
|
|
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.
|
|
|
|
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.
|
|
the variables CONFIGURE_ARGS, _DISTFILES, _PATCHFILES and
_PLIST_IGNORE_FILES to the +BUILD_INFO file.
Fixes PR 36228.
|
|
old behaviour back. Discussed on tech-pkg@.
|
|
normal build dependencies. That way digest can be recorded correctly.
|
|
|
|
|
|
hint where to look for the cause of the message. Without that, it is
next to useless.
|
