summaryrefslogtreecommitdiff
path: root/mk/check/check-files.mk
AgeCommit message (Collapse)AuthorFilesLines
2017-10-02mk: check for installed files that are not in PLIST by defaultwiz1-6/+2
Previously, this was only enabled with PKG_DEVELOPER. Ok kamil@ jperkin@
2017-06-14Essentially from OBATA Akio in private mail, June 2015:prlw11-1/+6
Introduce Icon Theme cache handling framework Icon Theme cache files are used by GTK+ and maintained with the gtk-update-icon-cache tool. Each Icon Theme package duplicates its own maintainance scripts: only the specified icon theme directory differs. With this framework, if packages have ICON_THEMES=yes, associated icon themes will be detected and their cache files will be maintained automatically. Change cache handling behaviour as follows: * Icon theme caches will be updated if either gtk2+ or gtk3+ gtk-update-icon-cache tool is available. * With installation of gtk2+ package, not only hicolor icon theme but also any other icon theme cache files will be updated. * Prevent removal of icon caches at deinstall, gtk3+ may be installed and using them. * Ditto with gtk3+, gtk2+ may not be installed now, so caches must be maintained by gtk3+.
2017-06-01Provide switch to activate new frameworks to replace "pkginstall".jlam1-2/+2
If ${_USE_NEW_PKGINSTALL} is "yes", then use the new "pkgtasks", "init", and "pkgformat/pkg"-scripts frameworks instead of the existing "pkginstall" framework.
2017-05-31Check that some variables have the correct number of words.jlam1-2/+6
Assert MAKE_DIRS_PERMS and OWN_DIRS_PERMS have the right number of words before using a multivariable .for loop over those variables. This prevents errors in parsing the makefiles.
2017-04-01Fixed typo.rillig1-3/+3
2014-10-12Simplify PKG_DEVELOPER checks.joerg1-3/+4
2014-02-20Prevent _CHECK_FILES_{PRE,POST} to include check-files-{pre,post}-messageobache1-5/+5
target, it is unwanted in check-files-clean target.
2013-03-08Add DESTDIR to error message in case of PLIST mismatch.wiz1-3/+3
Noted by Edgar Fuß.
2012-05-22mk/check/check-files.mk: Skip locale.aliasmarino1-1/+4
On DragonFly, packages like devel/doc++ and net/wap-utils were failing the file check during installation due to a present locale.alias file. Treat it the same as charset.alias.
2010-08-24I'm fed up with having to waste time because PKG_DEVELOPER is "special" andbad1-2/+2
can't be disabled by setting it to "no" like the other variables. Besides, flavor/pkg/metadata.mk has been expecting for a long time that "no" is a valid value. Make PKG_DEVELOPER DWIM.
2009-10-21revert previous - better do a bulk build with this change first to seetnn1-1/+4
if/how much stuff is dependent on it.
2009-10-21remove lib/charset.alias from CHECK_FILES_SKIPtnn1-4/+1
2009-05-08Remove a redundant "$" from a grep pattern.minskim1-2/+2
2008-02-08Skip ${PREFIX}/emul/linux32/proc.* as welladrianp1-3/+4
2008-02-07Replaced _PKG_SILENT and _PKG_DEBUG with RUN.rillig1-20/+20
2008-01-23STEP_MSG may be a hidden command.rillig1-5/+3
2007-09-27Even though VARBASE is sometimes below LOCALBASE, some users want torillig1-1/+3
check it. Don't prevent that in CHECK_FILES_STRICT=yes mode.
2007-09-12check-files shouldn't complain about files in VARBASE, since they cannotrillig1-1/+4
be represented in the PLIST.
2007-08-21Allow the existence of symlinks that point nowhere.jlam1-3/+3
2007-08-13Prevented the files check from being confused by concurrent instances ofrillig1-1/+3
"make replace". Since these are currently not locked properly, they may remove files from PKG_DBDIR while another package is being installed.
2007-03-16Added the variable declarations for the "show-all" target.rillig1-1/+5
2007-03-16Don't check files in ${PACKAGES} and ${DISTDIR}.rillig1-1/+5
2007-03-02Remove support for obsolete and unused NO_PKG_REGISTER.wiz1-16/+1
2007-01-06Moved the code that installs check-files on the hook from install.mk torillig1-1/+5
check-files.mk, for two reasons: 1. It belongs there. 2. Now check-files is run before check-perms and check-interpreter.
2006-12-15Remove trailing tabs.martti1-2/+2
2006-11-12Added a missing line continuation in the code for CHECK_FILES_STRICT.rillig1-2/+2
Apparently no one has been using that code since June 2006.
2006-11-09Added documentation.rillig1-8/+26
2006-10-09Main infrastructure for DESTDIR support.joerg1-6/+6
Packages may set PKG_DESTDIR_SUPPORT to either "destdir" or "user-destdir" to flag support for this, following the same rules as PKG_INSTALLATION_TYPES (e.g. define before first include of bsd.prefs.mk). The user activates it via USE_DESTDIR. When set to "yes", packages with "user-destdir" are handled as "destdir". The installation of the package will not go to ${LOCALBASE}, but a subdirectory of ${WRKDIR} instead. pre/post install scripts are not run and the package is not registered either. A binary package can be created instead to be installed normally with pkg_add. For "user-destdir" packages, everything is run as normal user and ownership is supposed to be correctled by pkg_create later. Since the current pkg_install code uses pax and it doesn't allow overwriting owners, this does not work yet. For "destdir" packages, installation, packaging and cleaning is run as root. This commit does not change the handling of DEPENDS_TARGET or bin-install to allow recursive usage.
2006-09-22- Compute CHEKCK_FILES filter on the entries requested and keep itjoerg1-4/+9
as tight as possible. Files we don't handle shouldn't be skipped. - fonts.alias is not created automatically, so don't remove it. - create fonts.encoding with mkfontdir using -e X11_ENCODINGSDIR. On platforms not following the X11R6 loayout this might need to be overriden. - Fix type1inst calls. - Modify packages which installed fonts.alias before to actually include it in the PLIST and bump the revisions accordingly. - Modify xorg-fonts* packages to use FONTS_DIRS.* to build indices at run time. Discussed with wiz and jlam.
2006-09-17Also ignore fontconfig cache like the "clasic" databases.joerg1-1/+2
2006-08-22Avoid spurious false negatives when the directories are reorderedjoerg1-4/+7
during install phase by sorting explicitly.
2006-06-09make(1) will automatically delete partially made targets if the targetjlam1-33/+19
creation fails, so remove instances where temporary files were created then moved to the final target filename, and just directly create the target. This is just for brevity/clarity, and saves a few tool calls.
2006-06-09Add a new variable CHECK_FILES_SUPPORTED which is a package-settablejlam1-1/+6
variable to show whether the package supports running the check-files target. Set CHECK_FILES_SUPPORTED to "no" in pkgtools/pkg_install in the case where the PREFIX does not match ${LOCALBASE} it's likely the tools are being installed in some place that's completely outside pkgsrc control, and check-files fails horribly in that case.
2006-06-09Introduce the capability to gather all the warnings and errors thatjlam1-25/+24
are generated for a target and output them all at once at the conclusion of the target's invocation. The implementation is in bsd.pkg.error.mk, which defines a macro target "error-check" that will print out any non-empty warning and error files in ${WARNING_DIR} and ${ERROR_DIR} and exit appropriately if there were errors. Convert some targets that were just long sequences of ${ERROR_MSG} or ${WARNING_MSG} within a single shell statement to use the new delayed error output via error-check. Modify the compiler "fail" wrappers for C++ and Fortran to be less verbose during invocation. Instead collect the warnings and only print them at the end of the completed phase, e.g. after "configure" and/or "build" completes.
2006-06-07Fix problems with check-files where it fails with a confusing messagejlam1-109/+157
that "the files are in the PLIST but not in ${PREFIX}" if the files that are installed overwrite other files already on the disk. Overwriting files can legitimately happen when, e.g. doing a "make update" or "make replace" without removing the old files, or when re-running "make install" after fixing a broken Makefile during development. While here, make the errors print to standard error using ERROR_CAT.
2006-06-03First pass at implementing support for package system flavors otherjlam1-0/+313
than pkgsrc's current one. This is an important lead-up to any project that redesigns the pkg_* tools in that it doesn't tie us to past design (mis)choices. This commit mostly deals with rearranging code, although there was a considerable amount of rewriting done in cases where I thought the code was somewhat messy and was difficult to understand. The design I chose for supporting multiple package system flavors is that the various depends, install, package, etc. modules would define default targets and variables that may be overridden in files from pkgsrc/mk/flavor/${PKG_FLAVOR}. The default targets would do the sensible thing of doing nothing, and pkgsrc infrastructure would rely on the appropriate things to be defined in pkgsrc/mk/flavor to do the real work. The pkgsrc/mk/flavor directory contains subdirectories corresponding to each package system flavor that we support. Currently, I only have "pkg" which represents the current pkgsrc-native package flavor. I've separated out most of the code where we make assumptions about the package system flavor, mostly either because we directly use the pkg_* tools, or we make assumptions about the package meta-data directory, or we directly manipulate the package meta-data files, and placed it into pkgsrc/mk/flavor/pkg. There are several new modules that have been refactored out of bsd.pkg.mk as part of these changes: check, depends, install, package, and update. Each of these modules has been slimmed down by rewriting them to avoid some recursive make calls. I've also religiously documented which targets are "public" and which are "private" so that users won't rely on reaching into pkgsrc innards to call a private target. The "depends" module is a complete overhaul of the way that we handle dependencies. There is now a separate "depends" phase that occurs before the "extract" phase where dependencies are installed. This differs from the old way where dependencies were installed just before extraction occurred. The reduce-depends.mk file is now replaced by a script that is invoked only once during the depends phase and is used to generate a cookie file that holds the full set of reduced dependencies. It is now possible to type "make depends" in a package directory and all missing dependencies will be installed. Future work on this project include: * Resolve the workflow design in anticipation of future work on staged installations where "package" conceptually happens before "install". * Rewrite the buildlink3 framework to not assume the use of the pkgsrc pkg_* tools. * Rewrite the pkginstall framework to provide a standard pkg_* tool to perform the actions, and allowing a purely declarative file per package to describe what actions need to be taken at install or deinstall time. * Implement support for the SVR4 package flavor. This will be proof that the appropriate abstractions are in place to allow using a completely different set of package management tools.
generated by cgit v1.2.3 (git 2.39.1) at 2024-08-21 16:48:09 +0000