summaryrefslogtreecommitdiff
path: root/mk/scripts
AgeCommit message (Collapse)AuthorFilesLines
2007-10-13The "debug" variable was often used like "if [ $debug = yes ]; then ...;rillig1-34/+19
fi". There is an easier way to solve the same problem with much less code.
2007-10-13The --database option doesn't exist.rillig1-3/+1
2007-10-09Remove trailing spaces.martti1-2/+2
2007-10-09Fixed CVS Id and trailing empty lines.rillig1-3/+1
2007-09-07Convert packages that test and use USE_INET6 to use the options frameworkjlam1-2/+2
and to support the "inet6" option instead. Remaining usage of USE_INET6 was solely for the benefit of the scripts that generate the README.html files. Replace: BUILD_DEFS+= USE_INET6 with BUILD_DEFS+= IPV6_READY and teach the README-generation tools to look for that instead. This nukes USE_INET6 from pkgsrc proper. We leave a tiny bit of code to continue to support USE_INET6 for pkgsrc-wip until it has been nuked from there as well.
2007-08-29The code for the pkg_install<20070714 vulnerability checks used in theadrianp1-2/+29
README.html generation are broken. It will not find vulnerabilities in any packages that have complex names in the pkg-vulnerabilties file. e.g. php{4,5}-perl and sun-{jdk,jre}15 Post pkg_install-20070714 this is now fixed and only currently known vulnerabilities are shown in the generated README.html files for packages. You will need to update to pkg_install>=20070714 to get this fix.
2007-08-02Be more intelligent when setting PVDIR. If pkg_install<20070714 then useadrianp1-6/+14
PKGVULNDIR; else extract the current setting using audit-packages -Q and use that. In addition to this mkreadme can still be called with -V to specify a pkg-vulnerabilities file that will override any automatic detection.
2007-08-02Don't bother using environment variables to pass info the shlib-typejlam1-11/+10
shell script. Just specify everything on the command line. Also, since shlib-type is a plain-old shell script with no bells and whistles, we can safely run it with "sh" and not "${SH}", which is necessary because "${SH}" isn't defined at this point.
2007-08-02Rewrite in a more portable way (basically cripple ourselves to Solarisjlam1-25/+21
/bin/sh).
2007-07-18Add back a facility to rebuild the run-time library search paths databasejlam1-0/+51
on platforms that need it. XXX Right now, if the platform needs it, then it runs for every package. XXX This needs to be fixed to only run for packages that install shared XXX libraries. * Move mk/plist/shlib-type to mk/scripts. * Move definition of SHLIB_TYPE from mk/plist/plist.mk to bsd.pkg.mk. * Move inclusion of bsd.pkginstall.mk below bsd.tools.mk so that it can use SHLIB_TYPE. This is necessary because SHLIB_TYPE's value is the result of evaluating a command, and the command needs "TOOL" definitions provided by bsd.tools.mk.
2007-05-28Remove trailing spaces.martti2-5/+5
2007-02-18* Add an extra -V option to mkreadme to support a non-standard PKGVULNDIRadrianp2-8/+33
* Add the necessary changes to allow genreadme.awk to process the v1.1.0 format pkg-vulnerabilities file. * Changes are fully backward compatable i.e. mkreadme should be able to parse v1.0.0 and v1.1.0 format files.
2007-01-08Don't mention -m in the example when the script does not support it.adrianp1-2/+2
2007-01-06Added the FAIL command, which can be prepended to an arbitrary shellrillig1-0/+5
command, making it return with a non-zero exit status. The first use of it is in a command called FAIL_MSG, which prints an error message and exits immediately. ERROR_MSG itself doesn't do that.
2006-12-15Remove trailing tabs.martti5-42/+42
2006-12-15Remove trailing spaces.martti6-35/+35
2006-10-22Removed setargs_from_cmd, as it is unused.rillig1-12/+1
2006-07-28Update the usage output to reflect current reality. Noted by Stoneddmcmahill1-4/+14
Elipot.
2006-07-28remove spurious empty line at the top of the summary filesdmcmahill1-2/+3
2006-07-28Allow the binpkg-cache script to also generate pkg_summary.gz filesdmcmahill3-19/+75
if requested. Suggested by Joerg Sonnenberger.
2006-07-01Add a script that can be used to scan for NO_BIN_ON_FTP packages usingdmcmahill1-0/+163
the cache files left by the README.html generation. This is indended to be used to monitor a ftp server, not for generating a file list for uploading to a ftp server.
2006-06-21When producing the list of directories containing binary packages, dodmcmahill1-3/+29
some extra processing to ensure that we have a list of unique directories. Otherwise we end up with two problems: - cache files get rebuilt all the time because they get built once for each path to the directory in question and since the path ends up in the cache, it is always declared out of date. - we end up with multiple links to the same binary package in the README.html files. Committed during the freeze becuase this is a real bug which is encountered daily.
2006-06-08undo most of the last commit which was a mistake.dmcmahill1-12/+3
2006-06-06When using find to search for the "All" directories containing binarydmcmahill1-4/+13
packages, use -follow. Hopefully this will pick up all of the binary packages again after the ftp.netbsd.org reorganization.
2006-06-06Refactor "fetch" and "extract" code into correspondingly namedjlam1-306/+0
subdirectories of pkgsrc/mk. Move the following files around for locality: pkgsrc/mk/scripts/extract -> pkgsrc/mk/extract/extract pkgsrc/mk/bsd.sites.mk -> pkgsrc/mk/fetch/sites.mk Also get rid of the recursive make for the "fetch" and "extract" targets. This basically merges the "fetch" and "extract" phases into the "patch" phase. There is still much more work to do to simplify the fetch code, but this is a good start.
2006-05-30Recognize -tar.gz as tar.gz files. PR 33571 by Dieter Roelants.wiz1-2/+2
2006-05-29when generating the list of pkgsrc packages, usedmcmahill1-29/+40
${BMAKE} show-subdir-var VARNAME=SUBDIR instead of just grepping through the makefiles. This seems to be a litle more robust. Suggested by Joerg Sonnenberger.
2006-05-28strip trailing comments when searching for SUBDIR+= lines in the Makefilesdmcmahill1-2/+2
2006-04-15Back to pkg-vulnerabilities format 1.0.0.salo1-4/+2
2006-03-22Remove an unsed script -- print-la-libnames was replaced withjlam1-77/+0
plist/libtool-expand after the plist module was committed.
2006-02-19Add .tar.bz supportadrianp1-3/+3
2006-02-04- Added "set -e" at the top of the file to prevent uncontrolled execution.rillig1-15/+28
- Added "set -u" at the top of the file to prevent spelling errors. - Renamed UNZIP to UNZIP_CMD, since that is used by the rest of pkgsrc. - Found a singleton use of $extract_options and replaced it with ${EXTRACT_OPTS_LHA}. - Took the default assignment for TMPDIR out of the block. All other entries are tools. - Removed unnecessary variables. - Make sure that distfile can always be resolved, even if the current working directory is changed. - Provide default values for all EXTRACT_OPTS_* variables, as close as possible to the point where they are used. - Replaced all "$@" with ${1+"$@"} to avoid errors when no parameters are given. - Made the removal of the temporary file for .tar extraction more robust.
2006-02-03.tar.z is a valid tar extension.joerg1-2/+2
2006-02-02Fix unrar usage: the command to extract is 'x', without hyphen.joerg1-2/+2
2006-01-24Ensure that decompress_cat and tarprog always have vaild default valuesjlam1-2/+3
in the case where the user makes bad option choices on the command line.
2006-01-23If the package directory doesn't exist, then return a non-zero code. Thisjlam1-2/+6
allows us to distinguish the case where everything is what we expect, and any deviations from that main case.
2006-01-23Handle *.ZIP the same way as *.zip -- fixes fonts/cyberbit-ttf extraction.wiz1-2/+2
2006-01-21While walking the dependency graph, push the dependencies onto thejlam1-2/+6
stack in the reverse order that show-depends-pkgpaths outputs them. This makes the top element of the stack the first child dependency that was marked as "pushed". This change orders the default "postfix" output of this script in such a way that for any package listed in the output, there is no earlier package that depends on it. In other words, you can take the default output and install from first to last and never need to install any dependencies, because any dependencies are guaranteed to have already been installed earlier.
2006-01-21duh... stacks are LIFOs not FIFOs.jlam1-2/+2
2006-01-21Allow using standard input for the archive contents for tar and sharjlam1-3/+16
extraction.
2006-01-21Fix the case where -X excludefile is used so that we don't error out tryingjlam1-3/+7
to remove "".
2006-01-21Teach the extract script how to exclude files specified on the commandjlam1-2/+14
line from extraction when using tar (it already knew how to do it for pax).
2006-01-21Teach extract how to extract *.z files using gzip.jlam1-3/+4
2006-01-21Teach the extract script a "-d dir" option to extract into a specificjlam1-2/+13
directory.
2006-01-21Fix up the comments, and add a fall-through for unrecognized archivejlam1-5/+10
formats.
2006-01-21Fix other instance of _ZOO -> _ZIP and remove a debugging line.jlam1-3/+2
2006-01-21unzip should be using EXTRACT_OPTS_ZIP, not *_ZOO.jlam1-2/+3
2006-01-21Teach the extract script to simply copy the distfile over to thejlam1-16/+40
current working directory by default if it can't figure out what type of archive it is. This handles the most common case of overriding EXTRACT_CMD in package Makefiles, which is to copy a C file or a Perl script over to the work directory. Also, modify the script to allow the file format to be specified on the command line via a -f option, which will force the extract script to interpret the archive as the specified a format. This covers the case where there is a distfile with an unusual file extension that is actually in well-known format, and we would like to just tell the extract script which format this is.
2006-01-20Teach this script a default extraction method for *.bin files (which arejlam1-2/+7
what Sun packagse its JRE/JDKs as). While here, cleanup up the comments slightly.
2006-01-20Support listing files/patterns for exclusion in an "excludefile",jlam1-7/+28
which is correctly parsed and translated into the correct syntax for the underlying tool.