Re: Joomla 1.0.12 from ports master sites is corrupted!!
Try to look at the contents of the file, it looks like response from some kind of redirection or response of some proxy server (the file should be probably html or ASCII text). Karel Ahmad Arafat Abdullah wrote: Today.. My task is to install Joomla on my FreeBSD 6.2-PRERELEASE box... previously it runs Joomla 1.5.x, installed thry source tarballs ( manually ) and my boss wat to change it to 1.0.12.. then i update ports, start to install 1.0.12.. but something weird happens.. # make install clean === Vulnerability check disabled, database not found === Extracting for joomla-1.0.12 = MD5 Checksum mismatch for joomla/Joomla_1.0.12-Stable-Full_Package.tar.bz2. === Refetch for 1 more times files: joomla/Joomla_1.0.12-Stable-Full_Package.tar.bz2 === Vulnerability check disabled, database not found = Joomla_1.0.12-Stable-Full_Package.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/joomla. = Attempting to fetch from http://forge.joomla.org/sf/frs/do/downloadFile/projects.joomla/frs.joomla_1_0.1_0_12/frs8162?dl=1/. fetch: http://forge.joomla.org/sf/frs/do/downloadFile/projects.joomla/frs.joomla_1_0.1_0_12/frs8162?dl=1/Joomla_1.0.12-Stable-Full_Package.tar.bz2: size unknown fetch: http://forge.joomla.org/sf/frs/do/downloadFile/projects.joomla/frs.joomla_1_0.1_0_12/frs8162?dl=1/Joomla_1.0.12-Stable-Full_Package.tar.bz2: size of remote file is not known Joomla_1.0.12-Stable-Full_Package.tar.bz2 7559 B 24 kBps === Vulnerability check disabled, database not found = MD5 Checksum mismatch for joomla/Joomla_1.0.12-Stable-Full_Package.tar.bz2. === Giving up on fetching files: joomla/Joomla_1.0.12-Stable-Full_Package.tar.bz2 Make sure the Makefile and distinfo file (/usr/ports/www/joomla/distinfo) are up to date. If you are absolutely sure you want to override this check, type make NO_CHECKSUM=yes [other args]. *** Error code 1 Stop in /usr/ports/www/joomla. *** Error code 1 Stop in /usr/ports/www/joomla. I test it on my other web/server ( I have 9 FreeBSD servers ) and the result is the same.. I've deleted Joomla source from distfiles, refetch again thru ports, still the same.. and suddenly ( after one whole day ).. I try to download it manually from joomla sites itself, I reveal something.. the filesize is much more bigger!! MD5 Checksum also shown that the files is corrupted... Joomla_1.0.12-Stable-Full_Package.tar.bz2 7559 B 24 kBps previous then i download it from: http://joomlacode.org/gf/download/frsrelease/111/264/Joomla_1.0.12-Stable-Full_Package.tar.bz2 -rw-r--r-- 1 root wheel 1.6M Apr 15 19:09 Joomla_1.0.12-Stable-Full_Package.tar.bz2 in my distfiles after i download it manually after that seems all my installation process runs smoothly.. no hiccup at all.. anyone also face the same thing? Seems some of the developers ( ports etc ) need to inform the masters sites about this... TQ Arafat System and Network Engineer ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Mailman virtual-mailman.db
I am missing something in facilitating the creation of virtual-mailman.db. I get the failure line in maillog fatal: open database /usr/local/mailman/data/virtual-mailman.db I have gonne through the docs but am obviously missing something. Could anyone please let me know: 1. How virtual-mailman.db is created 2. Ideally some examples from relevant config files would be ideal. I do seem to ne struggling with mailman!!! Thanks in advance David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
ports/111417 [PATCH] security/vscan: Update update_dat for 5000 dat Files
Can I interest a committer in a quick patch? ports/111417[PATCH] security/vscan: Update update_dat for 5000 dat files This patches the update_dat script to deal with version numbers greater than 5000, which happened a couple of weeks ago. Thanks! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 512-248-2683E-Mail: [EMAIL PROTECTED] US Mail: 430 Valona Loop, Round Rock, TX 78681-3893 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade -s broken in portupgrade 2.2.6
hihi. Is portupgrade -s still supported and/or known to be working in portupgrade 2.2.6? Currently I have two machines using portupgrade 2.2.6 all my others are using pre-2.0 versions. The new machines show this problem. The old ones work fine. If I do a portupgrade -vsb portname it'll terminate with this: --- Build of databases/ruby-bdb ended at: Tue, 17 Apr 2007 10:19:53 -0500 (consumed 00:00:10) --- Uninstallation of ruby18-bdb-0.5.9_2 started at: Tue, 17 Apr 2007 10:19:53 -0500 --- Uninstallation of ruby18-bdb-0.5.9_2 ended at: Tue, 17 Apr 2007 10:19:53 -0500 (consumed 00:00:00) --- Reinstallation of databases/ruby-bdb ended at: Tue, 17 Apr 2007 10:19:53 -0500 (consumed 00:00:10) --- ** Upgrade tasks 1: 0 done, 0 ignored, 0 skipped and 1 failed --- Listing the results (+:done / -:ignored / *:skipped / !:failed) ! databases/ruby-bdb (ruby18-bdb-0.5.9_2) (Permission denied) --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed --- Session ended at: Tue, 17 Apr 2007 10:19:53 -0500 (consumed 00:00:11) /usr/local/sbin/portupgrade:2084: [BUG] Segmentation fault ruby 1.8.5 (2006-12-25) [i386-freebsd6] Looking at the system logs portupgrade isn't trying to run any commands using sudo. If I try upgrading a port with sudo portupgrade -vb portname it'll work. Thanks! -- James. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mailman virtual-mailman.db
On Apr 17, 2007, at 7:29 AM, Vizion wrote: I am missing something in facilitating the creation of virtual- mailman.db. I get the failure line in maillog fatal: open database /usr/local/mailman/data/virtual-mailman.db I have gonne through the docs but am obviously missing something. Could anyone please let me know: 1. How virtual-mailman.db is created The answer below assumes that you are also using postfix It is created from /usr/local/mailman/data/virtual-mailman (assuming you haven't modified the install location and installed from ports), which mailman should also create for you. Mailman actually calls the postfix utility, postmap, to generate the .db file. To create these files the first time, run /usr/local/mailman/bin/genaliases which should create these files. 2. Ideally some examples from relevant config files would be ideal. I do seem to ne struggling with mailman!!! Mailman takes a fair amount of post installation configuration, requiring fairly solid understanding of mail transport, apache and, it seems, mailman itself. So it is easy to overlook things in the documentation, but this is in /usr/local/share/doc/mailman/mailman-install.txt Cheers, -j ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re: Mailman virtual-mailman.db
From: Jeffrey Goldberg [EMAIL PROTECTED] Date: 2007/04/17 Tue AM 08:51:42 PDT To: Vizion [EMAIL PROTECTED] CC: freebsd-ports@freebsd.org Subject: Re: Mailman virtual-mailman.db On Apr 17, 2007, at 7:29 AM, Vizion wrote: I am missing something in facilitating the creation of virtual- mailman.db. I get the failure line in maillog fatal: open database /usr/local/mailman/data/virtual-mailman.db I have gonne through the docs but am obviously missing something. Could anyone please let me know: 1. How virtual-mailman.db is created The answer below assumes that you are also using postfix It is created from /usr/local/mailman/data/virtual-mailman (assuming you haven't modified the install location and installed from ports), which mailman should also create for you. Mailman actually calls the postfix utility, postmap, to generate the .db file. To create these files the first time, run /usr/local/mailman/bin/genaliases which should create these files. 2. Ideally some examples from relevant config files would be ideal. I do seem to ne struggling with mailman!!! Mailman takes a fair amount of post installation configuration, requiring fairly solid understanding of mail transport, apache and, it seems, mailman itself. So it is easy to overlook things in the documentation, but this is in /usr/local/share/doc/mailman/mailman-install.txt Cheers, -j Thanks for getting back so quickly For some reason /usr/local/mailman/bin/genaliases does not create that file.. I think I am missing something else. I could send some more info if you would be willing to take a look david ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
How to clean ...
How to delete old files, I have the list in the pkg-plist and I wan to delete files older than a specified date which are in the list? I can't re-install because it can upgrade files which I wan to keed (newer than the date). Does an utility do this? -- regis ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [wine] can't run /libexec/ld-elf.so.1 not found
On Tue, 17 Apr 2007 13:24:25 +0200 regisr [EMAIL PROTECTED] wrote: When I launch wine just build from ports tree (cvsup yesterday) installed with portupgrade, I have the following error message: ELF interpreter /libexec/ld-elf.so.1 not found But the lib is in right place... It is the only program which can't run! %ls -l /libexec//ld* -r-xr-xr-x 1 root wheel 159800 27 jan 11:25 /libexec//ld-elf.so.1 -r-xr-xr-x 1 root wheel 158712 12 nov 14:01 /libexec//ld-elf.so.1.old What I do wrong? It's well-known problem. The maximum hard-limit data size (kern.maxdsiz) is too big (over about 1GB). So you may set kern.maxdsiz=805306368 to your /boot/loader.conf. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Mailman virtual-mailman.db
On Apr 17, 2007, at 10:58 AM, Vizion wrote: From: Jeffrey Goldberg [EMAIL PROTECTED] On Apr 17, 2007, at 7:29 AM, Vizion wrote: I get the failure line in maillog fatal: open database /usr/local/mailman/data/virtual-mailman.db To create these files the first time, run /usr/local/mailman/bin/genaliases Thanks for getting back so quickly For some reason /usr/local/mailman/bin/genaliases does not create that file.. See if the file data/virtual-aliases exists. If it doesn't just created it as an empty file and make sure that it is readable by the mailman group. Then try genaliases again. If that doesn't work, just remove the reference to data/virtual- aliases in your postfix main.cf. That will just be a temporary fix, because later you may need virual-aliases. Can you post an ls -l of your mailman/data directory? Cheers, -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
mailman
I am having problems getting /data/virtual-mailman.db created. Here are the errors I am getting from maillog: Apr 17 05:09:23 dns1 postfix/master[687]: reload configuration /usr/local/etc/postfix Apr 17 05:09:34 dns1 postfix/cleanup[3738]: fatal: open database /usr/local/mailman/data/virtual-mailman.db: No such file or directory Apr 17 05:09:35 dns1 postfix/master[687]: warning: process /usr/local/libexec/postfix/cleanup pid 3738 exit status 1 Apr 17 05:09:35 dns1 postfix/master[687]: warning: /usr/local/libexec/postfix/cleanup: bad command startup -- throttling Apr 17 05:09:52 dns1 postfix/smtpd[3739]: fatal: open database /usr/local/mailman/data/virtual-mailman.db: No such file or directory Apr 17 05:09:53 dns1 postfix/master[687]: warning: process /usr/local/libexec/postfix/smtpd pid 3739 exit status 1 Apr 17 05:09:53 dns1 postfix/master[687]: warning: /usr/local/libexec/postfix/smtpd: bad command startup -- throttling Could anyone please tell me what I need to check, the process by which virtual-mailman.db is created. If possible an example from the relevant config files would be really appreciated. Thanks in advance David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mailman
On Apr 17, 2007, at 5:14 AM, David Southwell wrote: Could anyone please tell me what I need to check, the process by which virtual-mailman.db is created. If possible an example from the relevant config files would be really appreciated. There should be a file called virtual-mailman which contains the text of the virtual aliases or whatever is supposed to be there-- you then run postmap virtual-mailman in that location, which will take the text file and process it into a Postfix database (typically BerkeleyDB). -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
grace 5.1.21 port
Hello: I do not know if this e-mail account is a mail-list or a personal e-mail. Anyway, I woul like to say to the maintainer of this port to upgrade it to the newest recent version, i.e. 5.1.21. Thanks a lot for your work! cheers Xavier ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade -s broken in portupgrade 2.2.6
James wrote: hihi. Is portupgrade -s still supported and/or known to be working in portupgrade 2.2.6? Currently I have two machines using portupgrade 2.2.6 all my others are using pre-2.0 versions. The new machines show this problem. The old ones work fine. Well, I don't know where this regression has happened but it has. I'll add a note in my TODO list. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
upgrade Gimp does work like mentioned in UPDATING
hi, Problem Gimp. in UPDATING: , | 20070404: | AFFECTS: users of graphics/gimp and graphics/gimp-devel | AUTHOR: [EMAIL PROTECTED] | | The gimp[-devel] port is now a meta-port so users will need to upgrade via | one of the following examples. Gimp now depends on gutenprint instead of | gimp-print, if you have gimp-print installed you will need to | pkg_delete gimp-print before you install or upgrade the gimp. | |. | portupgrade users: |(gimp) | portupgrade -o graphics/gimp-app gimp | portupgrade -u graphics/gimp ` Dowas not work: Line 1: , | portupgrade -o graphics/gimp-app gimp | ** Detected a package name change: gimp (graphics/gimp) - 'gimp-app' (graphics/gimp-app) | ** No need to upgrade 'gimp-2.2.13_2,1' (= gimp-app-2.2.13_2,1). (specify -f to force) | [EMAIL PROTECTED] ~]# ` Second Line: , | portupgrade -u graphics/gimp | | SNIP | | gimp-2.2,2: Old version of gimp detected! Please see /usr/ports/UPDATING for information on upgrading gimp-2.2,2 | *** Error code 1 | | Stop in /usr/ports/graphics/gimp. | *** Error code 1 | | Stop in /usr/ports/graphics/gimp. | ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade.35556.0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gimp-2.2.13_2,1 UPGRADE_PORT_VER=2.2.13_2,1 make | ** Fix the problem and try again. | ** Listing the failed packages (*:skipped / !:failed) | ! graphics/gimp (gimp-2.2.13_2,1) (unknown build error) | --- Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed | [EMAIL PROTECTED] ~]# ` What to do? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mailman
On Tuesday 17 April 2007 09:55:38 Chuck Swiger wrote: On Apr 17, 2007, at 5:14 AM, David Southwell wrote: Could anyone please tell me what I need to check, the process by which virtual-mailman.db is created. If possible an example from the relevant config files would be really appreciated. There should be a file called virtual-mailman which contains the text of the virtual aliases or whatever is supposed to be there-- you then run postmap virtual-mailman in that location, which will take the text file and process it into a Postfix database (typically BerkeleyDB). I just want to say a big thank to you to everyone else who chipped in and helped. I now have the problem fingers crossed solved and a working mailman/postfix comnination You guys have been terrific. Thanks abundle David ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [wine] can't run /libexec/ld-elf.so.1 not found
On Wed, 18 Apr 2007 00:58:19 +0900 Norikatsu Shigemura [EMAIL PROTECTED] a écrit: It's well-known problem. The maximum hard-limit data size (kern.maxdsiz) is too big (over about 1GB). So you may set kern.maxdsiz=805306368 to your /boot/loader.conf. Thanks. It is working. Why I can't found this hint??? This is a problem for me because I need a big data size for gutenprint when I print A3 with 8 inks! -- regis ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Utility for safe updating of ports in base system
All: I was just on the FreeBSD list of projects and ideas fot volunteers page and I was wondering if anyone was working on the portupgrade in C utility. I would be willing to help (code/document/test) if it's needed. A -- Adam P. Stroud Intelligent Systems Division BAE Systems, Advanced Information Technologies 6 New England Executive Park Burlington, MA 01803 781.273.3388 x522 [EMAIL PROTECTED] smime.p7s Description: S/MIME Cryptographic Signature
Re: [wine] can't run /libexec/ld-elf.so.1 not found
It's well-known problem. The maximum hard-limit data size (kern.maxdsiz) is too big (over about 1GB). So you may set kern.maxdsiz=805306368 to your /boot/loader.conf. Ok I find the following PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=94413 May be this info should be added in the pkg-message. -- regis ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Utility for safe updating of ports in base system
On Tue, 17 Apr 2007 14:31:39 -0400 Adam Stroud [EMAIL PROTECTED] wrote: I was just on the FreeBSD list of projects and ideas fot volunteers page and I was wondering if anyone was working on the portupgrade in C utility. I would be willing to help (code/document/test) if it's needed. What would be the point of putting any port-upgrading tool in the base-system? The ports tree isn't branched, so why branch such tools in the base-system. IMO they logically belong in ports where they are better able to follow any developments in the ports-system. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Utility for safe updating of ports in base system
On 4/18/07, Adam Stroud [EMAIL PROTECTED] wrote: All: I was just on the FreeBSD list of projects and ideas fot volunteers page and I was wondering if anyone was working on the portupgrade in C utility. I would be willing to help (code/document/test) if it's needed. I think that some projects were started, but did not go very far. The current consensus is that portmaster, which is a collection of sh scripts, should be further developed and eventually committed to the base system. The developer of portmaster is one of those who does not really like that idea. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrade Gimp does work like mentioned in UPDATING
On Tuesday, 17. April 2007, Heino Tiedemann wrote: hi, Problem Gimp. in UPDATING: , | 20070404: | AFFECTS: users of graphics/gimp and graphics/gimp-devel | AUTHOR: [EMAIL PROTECTED] | | The gimp[-devel] port is now a meta-port so users will need to upgrade | via one of the following examples. Gimp now depends on gutenprint instead | of gimp-print, if you have gimp-print installed you will need to | pkg_delete gimp-print before you install or upgrade the gimp. | |. | portupgrade users: |(gimp) | portupgrade -o graphics/gimp-app gimp | portupgrade -u graphics/gimp [...] Does not work [...] What to do? pkg_deinstall -f gimp-print ; portupgrade -o graphics/gimp-app -fO gimp portupgrade -N graphics/gimp -- ,_, | Michael Nottebrock | [EMAIL PROTECTED] (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org pgpoVaup2bE2F.pgp Description: PGP signature
Re: Utility for safe updating of ports in base system
RW wrote: On Tue, 17 Apr 2007 14:31:39 -0400 Adam Stroud [EMAIL PROTECTED] wrote: I was just on the FreeBSD list of projects and ideas fot volunteers page and I was wondering if anyone was working on the portupgrade in C utility. I would be willing to help (code/document/test) if it's needed. What would be the point of putting any port-upgrading tool in the base-system? The ports tree isn't branched, so why branch such tools in the base-system. IMO they logically belong in ports where they are better able to follow any developments in the ports-system. I'm working on combining the pkg_* tools along with the existing makefile system with a bourne shell file for my SoC project(*) As for writing a utility in C, why? Almost everything's there right now and just needs to be strung together with some clever scripting to make it all work. C in this case is just overkill IMO. I'm sorry RW, because while I do agree to some extent, there should be something out of the box that works with the Makefiles and does everything necessary to install ports, apart from someone manually going to each directory and typing in make install, or using some advanced functionality in the Makefiles. (*) This is the 2nd goal on my list out of 3 items, so it's going to be a while before I get to it (I estimate 2 months). -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Tracking port and package flags/options
[Please maintain CC.] Here are some patches to the FreeBSD package tools, and the ports infrastructure to track make flags/options used to build a port/package. I've been using these changes locally for something like 2-3 years. This greatly helps me manage packages across several machines, and across port upgrades. There are some quirks, such as recursively built ports inherit the port flags used for the explicitly built port. Sometimes this recursive behavior is intentional, but most often the implicitly built ports do not necessarily use the flags for the explicitly built port. There are also two other unrelated tweaks to the ports infrastructure in the patch, but I've included them as I've been using them for a long time as well. First is to make backups when using USE_DOS2UNIX. Second is to change dependency tracking to first-order only (versus recursive); see http://docs.freebsd.org/cgi/mid.cgi?427E4687.40901 for previous discussion. I'm posting these now, as I see there are at least two SoC projects aimed at the ports/package infrastructure, and perhaps these changes (conceptual or implementation) could be considered by the SoC participants for incorporation. -James # # Updates to FreeBSD package tools to track compile flags/options # for ports/packages. # # Submitted By: James Flemer [EMAIL PROTECTED] # Index: usr.sbin/pkg_install/add/perform.c === RCS file: /home/ncvs/src/usr.sbin/pkg_install/add/perform.c,v retrieving revision 1.77.8.3 diff -u -b -u -r1.77.8.3 perform.c --- usr.sbin/pkg_install/add/perform.c 14 May 2006 06:52:24 - 1.77.8.3 +++ usr.sbin/pkg_install/add/perform.c 18 Apr 2007 02:30:02 - @@ -238,6 +238,8 @@ Plist.name = anonymous; if (Plist.origin == NULL) Plist.origin = anonymous/anonymous; +if (Plist.makeflags == NULL) + Plist.makeflags = ; /* * See if we're already registered either with the same name (the same Index: usr.sbin/pkg_install/create/create.h === RCS file: /home/ncvs/src/usr.sbin/pkg_install/create/create.h,v retrieving revision 1.25.2.1 diff -u -b -u -r1.25.2.1 create.h --- usr.sbin/pkg_install/create/create.h 11 Nov 2005 08:07:24 - 1.25.2.1 +++ usr.sbin/pkg_install/create/create.h 18 Apr 2007 02:30:02 - @@ -41,6 +41,7 @@ extern char *Pkgdeps; extern char *Conflicts; extern char *Origin; +extern char *Makeflags; extern char *InstalledPkg; extern char PlayPen[]; extern int Dereference; Index: usr.sbin/pkg_install/create/main.c === RCS file: /home/ncvs/src/usr.sbin/pkg_install/create/main.c,v retrieving revision 1.36.2.2 diff -u -b -u -r1.36.2.2 main.c --- usr.sbin/pkg_install/create/main.c 14 May 2006 07:01:47 - 1.36.2.2 +++ usr.sbin/pkg_install/create/main.c 18 Apr 2007 02:30:02 - @@ -16,7 +16,7 @@ #include lib.h #include create.h -static char Options[] = EGYNORhjvxyzf:p:P:C:c:d:i:I:k:K:r:t:X:D:m:s:S:o:b:; +static char Options[] = EGYNORhjvxyzf:p:P:C:c:d:i:I:k:K:r:t:X:D:m:s:S:o:F:b:; match_t MatchType = MATCH_GLOB; char *Prefix = NULL; @@ -36,6 +36,7 @@ char *Pkgdeps = NULL; char *Conflicts = NULL; char *Origin = NULL; +char *Makeflags = NULL; char *InstalledPkg = NULL; char PlayPen[FILENAME_MAX]; int Dereference = FALSE; @@ -163,6 +164,10 @@ Origin = optarg; break; + case 'F': + Makeflags = optarg; + break; + case 'y': case 'j': Zipper = BZIP2; @@ -231,7 +236,7 @@ usage: pkg_create [-YNOhvyz] [-P pkgs] [-C conflicts] [-p prefix] , [-i iscript] [-I piscript] [-k dscript] [-K pdscript] , [-r rscript] [-t template] [-X excludefile] , - [-D displayfile] [-m mtreefile] [-o origin] , + [-D displayfile] [-m mtreefile] [-o origin] [-F flags], [-s srcdir] [-S basedir] , -c comment -d description -f packlist pkg-filename, pkg_create [-EGYNhvxyzR] -b pkg-name [pkg-filename]); Index: usr.sbin/pkg_install/create/perform.c === RCS file: /home/ncvs/src/usr.sbin/pkg_install/create/perform.c,v retrieving revision 1.80.2.2 diff -u -b -u -r1.80.2.2 perform.c --- usr.sbin/pkg_install/create/perform.c 10 Jan 2006 22:15:05 - 1.80.2.2 +++ usr.sbin/pkg_install/create/perform.c 18 Apr 2007 02:30:03 - @@ -210,6 +210,10 @@ if (Prefix) add_plist_top(plist, PLIST_CWD, Prefix); +/* Add the make flags if asked, at the top */ +if (Makeflags) + add_plist_top(plist, PLIST_MAKEFLAGS, Makeflags); + /* Add the origin if asked, at the top */ if (Origin) add_plist_top(plist, PLIST_ORIGIN, Origin); Index: usr.sbin/pkg_install/create/pkg_create.1 === RCS file:
