How to get errors printed
I'm having trouble with the devel/kdesdk4 port, in trying to update it from the 4.2.1 to the latest in ports which is 4.3.4. I'm using portupgrade, but the port itself uses cmake to build itself. At first, it gave me no useful output at all (I hate any make tool that goes out of it's way to hide errors!), but I found that if you define VERBOSE=1, you can at least get the command line given to shell to print, so I can now see all the calls to c++. The trouble is, I can't see ANY of the error output (VERBOSE apparently doesn't help there). There's gotta be some way to manipulate cmake to report it's errors. I CAN say that I *think* the build is breaking immediately after it announces that it's built kbugbuster, but I can't tell if the build actually dies doing kbugbuster, or doing whatever it is that comes after bugbuster. There is one fishy thing I can report: in the previous lines to the cm,ake report on kbugbuster, there's a command to c++ that seems to be linking kbugbuster, and it's got one phrase that's odd: -Wl,-rpath,/usr/local/kde4/lib:/usr/local/lib/qt4 All those colons, it strikes me as fishy. I see nothing in my environment that gives any hint, I'm using FreeBSD-current, with gcc-4.2.1. So, either (if you can) tell me how I can get cmake to print out the errors in a make run, OR give me a guess as to what might have caused that wierd phrase in the kbugbuster linking command. Thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ioquake3 support more platforms
Doug Barton wrote: > Dominic Fandrey wrote: >> But this is not the case we're talking about (I explained the process >> in sufficient detail, I think). I take an up to date snapshot, apply my >> patch set, make a couple of test builds and runs, update the patch set >> until everything works as expected. Than I wrap the whole thing (SVN >> snapshot and my patches) up in a tar.gz and upload it to an ftp server. > > Well then I misunderstood what was proposed, and I apologize for that. > What you described is supported, and some ports are already doing it. I'm really glad this is just a misunderstanding, I was about to panic. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
portupgrade's logging
according to portupgrade's man page, the -l option sets to have the output of a portupgrade session, but when I try it, I don't get anything there. Is there something I'm doing wrong, something that I am overlooking? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: bsd.sites.mk
On Sat, 19 Dec 2009 16:11:42 -0700 "John J. Rushford Jr" wrote: > Greetings, > > I was wondering if you could move ftp.belnet.be to the bottom of all > lists in bsd.sites.mk. This ftp site is extremely slow and shouldn't > be at the top of the list in my opinion. > Try setting your preferred servers in MASTER_SORT_REGEX. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
bsd.sites.mk
Greetings, I was wondering if you could move ftp.belnet.be to the bottom of all lists in bsd.sites.mk. This ftp site is extremely slow and shouldn't be at the top of the list in my opinion. thanks John Rushford j...@alisa.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADS UP] Experimental 3D HW accel support for Radeon HD 2xxx, 3xxx and 4xxx.
On Sun, Dec 06, 2009 at 01:14:39PM -0500, Robert Huff wrote: > > =?ISO-8859-1?Q?Marius_N=FCnnerich?= writes: > > > One thing I know is interesting for many people is playing World > > of Warcraft under wine. Last time I checked it wasn't even > > possible under linux with catalyst. Do you know anything about > > this or have tried it? > > I am not 100% certain - I use neither WoW or Linux - but I > believe this is incorrect. I think a friend of a friend has this > working. I can confirm that - I used to run WoW in WINE on the fglrx drivers without a hitch. This was about 4 years ago on an All-in-Wonder 9600. I'd hope they haven't regressed that badly. ;) -- Richard Kolkovich sarum...@sigil.org PGP Key: 0x9E54EF59 (http://pgp.mit.edu) pgpnqe9xpRiHe.pgp Description: PGP signature
Re: [RFC] PHP 5.3
Hi, sorry to jump in late.. On Wednesday 02 December 2009 04:52:35 Alex Dupre wrote: > Gergely CZUCZY ha scritto: > >> Oh come on. Security-wise you shouldn't hold php at all. It's about > >> backwards incompatibility, not about security. > > PHP 5.3 is not more incompatible with 5.2 than 5.2 was with 5.1 (and 5.1 > with 5.0). 5.2 branch will be dropped in near future, so I'm not going > to maintain 80 (eighty) additional ports just for fun. Would it be interesting to see which ports break with 5.3 and fix these or mark them broken before/at the same time 5.3 hits the tree? Also, the impact of the 5.3 incompatibilities is much larger then 5.1 to 5.2, even though the number is similar. -- Mel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ioquake3 support more platforms
Dominic Fandrey wrote: > But this is not the case we're talking about (I explained the process > in sufficient detail, I think). I take an up to date snapshot, apply my > patch set, make a couple of test builds and runs, update the patch set > until everything works as expected. Than I wrap the whole thing (SVN > snapshot and my patches) up in a tar.gz and upload it to an ftp server. Well then I misunderstood what was proposed, and I apologize for that. What you described is supported, and some ports are already doing it. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portmaster-with-package-support release candidate available for testing / pkg_add: illegal option -- -
Miroslav Lachman wrote: > I don't know if it is well known / documented somewhere in portmaster, > but after debugging, I realized that pkg_add on FreeBSD 6.3 has no long > options This is why all of the ports tools should be in the ports tree. :) I just added the fix to the svn version of portmaster, if you can confirm that it works I'll add it to the port immediately. I was not aware of this issue, and apparently you're the first person to test package support on a release this old. Thank you, both for the testing and the bug report. > And one question - is it really mandatory to use > --local-packagedir=/usr/ports/packages if I want to install locally > available packages from standard path /usr/local/packages/All? Yes. > Shouldn't it be default behavior? IMO, no. I think that the vast majority of FreeBSD users just want to be able to fetch packages and have them installed. > Without --local-packagedir portmaster is trying to fetch it from FTP: > "Package and/or archive not found at: > http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.3-release/lang/"; > and doesn't look at the local directory: > "There is no valid package to install, building port instead" This is the desired behavior. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: How do I make npviewer.bin respect $TMPDIR ??
On Thu, Dec 17, 2009 at 12:55 PM, Ulrich Spörlein wrote: > On Sun, 06.12.2009 at 12:18:21 -0800, Doug Barton wrote: >> Howdy, >> >> I'm -current, i386, linux_base-f10-10_2, and >> linux-f10-flashplugin-10.0r32; all with the latest firefox 35. It all >> works fine, until my teeny tiny (24M) memory disk /tmp gets full. >> >> I have created a wrapper script for firefox to set TMPDIR (and TMP and >> TEMPDIR just in case) to a large partition on local disk, which works >> for firefox proper, but npviewer.bin is still putting its temp files >> on the real /tmp. So, how do I whip it into shape? > > Haven't tried this, but there's a slight chance that the linux binary > will prefer /compat/linux paths over / paths, and since there seems to > be no /compat/linux/tmp, please try creating or symlinking one ... Or put something like this in /etc/fstab: /tmp/usr/compat/linux/tmpnullfsrw00 -- My preferred quotation of Robert Louis Stevenson is "You cannot make an omelette without breaking eggs". Not because I like the omelettes, but because I like the sound of eggs being broken. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ioquake3 support more platforms
On Sat, Dec 19, 2009 at 04:02:31PM +0100, Dominic Fandrey wrote: > I don't see the wiggle room for anything spontaneously changing when > properly checksummed distfiles are involved. Alright, then I misread it. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: portmaster-with-package-support release candidate available for testing / pkg_add: illegal option -- -
Doug Barton wrote: Howdy! I'm very excited to announce that what I hope to be the final version of the new portmaster with package support is now available for testing. I've done quite a bit of regression testing myself, but the last time I posted about the beta version several people were kind enough to give it a go and I got several really good suggestions. It would be really great if more users could give this version a try before I commit it to the actual port. You can find the information on accessing the svn version at http://dougbarton.us/portmaster-proposal.html [...] Hi Doug, I gave it a try, but no luck :) I tried portmaster --local-packagedir=/usr/ports/packages -P python26-2.6.2_3 and got error message: ===>>> Currently installed version: python26-2.6.2_3 ===>>> Port directory: /usr/ports/lang/python26 ===>>> Gathering dependency list for lang/python26 from ports ===>>> No dependencies for lang/python26 ===>>> Starting build and/or install for lang/python26 <<<=== ===>>> All dependencies are up to date ===>>> Checking package repository for latest available version ===>>> Available package (python26-2.6.4) matches the ports tree ===>>> Creating a backup package for old version python26-2.6.2_3 ===>>> Package saved to /usr/ports/packages/portmaster-backup pkg_delete: package 'python26-2.6.2_3' is required by these other packages and may not be deinstalled (but I'll delete it anyway): python-2.6,2 ===>>> Installing package pkg_add: illegal option -- - usage: pkg_add [-vInrfRMSK] [-t template] [-p prefix] [-P prefix] [-C chrootdir] pkg-name [pkg-name ...] ===>>> A backup package for python26-2.6.2_3 should be located in /usr/ports/packages/portmaster-backup ===>>> Installation of python26-2.6.4.tbz (lang/python26) failed ===>>> Aborting update I don't know if it is well known / documented somewhere in portmaster, but after debugging, I realized that pkg_add on FreeBSD 6.3 has no long options (--no-deps --force), there is only -f, but no -i. If it can't be worked around, than packages support on FreeBSD < 7 should be completely disabled. Tested in jailed FreeBSD 6.3-RELEASE-p5 with portmaster Version 2.15 And one question - is it really mandatory to use --local-packagedir=/usr/ports/packages if I want to install locally available packages from standard path /usr/local/packages/All? Shouldn't it be default behavior? Without --local-packagedir portmaster is trying to fetch it from FTP: "Package and/or archive not found at: http://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.3-release/lang/"; and doesn't look at the local directory: "There is no valid package to install, building port instead" Miroslav Lachman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ioquake3 support more platforms
b. f. wrote: >> On Fri, Dec 18, 2009 at 02:50:31PM +0100, Dominic Fandrey wrote: >>> So when I submitted ioquake3-1.36 I condemned some poor committer >>> to read 366609 lines of code? >> We expect them to test-install the initial code to make sure it's >> not malware. >> >> We expect them to scan the diffs to make sure the system isn't rooted. > >> What's your alternate suggestion? Just let everyone commit whatever >> they want and hope for the best? > > Aren't the two of you talking at cross-purposes here? It seems to me > that the OP is looking for a way to update a port to a distfile > created from a snapshot of project sources -- not in the sense of > sources that are recreated each and every build by fetching a snapshot > from a remote VCS, but an actual tarball that has been audited, > checksummed, and uploaded to a project server. Surely this is needed > for a few ports, including some now in the tree? I have the same impression. I'm wondering how this could be the case. In the OP I wrote: > I'm providing distfiles, ... I don't see the wiggle room for anything spontaneously changing when properly checksummed distfiles are involved. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ioquake3 support more platforms
Doug Barton wrote: > Dominic Fandrey wrote: >> But that's not different for any port. E.g. sysutils/bsdadminscripts is >> all mine, I create the distfiles and maintain the port, their is no >> guarantee that I don't do evil apart from me being quite certain that >> I don't. > > Mark already pointed out that maintainers and committers actually _do_ > have a responsibility to dig into changes, be knowledgeable about > upgrades, etc. I agree with his perspective on this. > >> Why can one assume that an ioquake release is safe? One really cannot. >> It's made by the same people who maintain the non-trustworthy SVN. >> >> What if I created a sourceforge project freebsd-ioquake and published >> my distfiles there as ioquake freebsd releases. Would it suddenly >> turn trustworthy? > > The security problems involved in trying to audit a fixed, known set > of files are miniscule compared to the problems involved in auditing a > set of files that can change on a minute by minute basis. The whole > concept of creating a FreeBSD port that checks source files out of a > third-party svn repository is anathema to the whole concept of ports > security. Even if the files were directly checked out from SVN, they'd be checked out from a tested point in time. But this is not the case we're talking about (I explained the process in sufficient detail, I think). I take an up to date snapshot, apply my patch set, make a couple of test builds and runs, update the patch set until everything works as expected. Than I wrap the whole thing (SVN snapshot and my patches) up in a tar.gz and upload it to an ftp server. There's no danger that anything changes. I'm not about to break md5 and sha256. -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
INDEX now builds successfully on 6.x
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Need help with a port
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Dec 18, 2009 at 07:16:37PM -0600, Paul Schmehl wrote:
> --On December 18, 2009 5:10:39 PM -0600 Greg Larkin
> wrote:
> >
> > Hi Paul,
> >
> > "make -V BINMODE" returns "555", so as long as you're OK with those
> > permissions, I would say using the ${BINMODE} macro is preferable.
> > Otherwise, there's no issue with you using the correct permissions value
> > (755, +x, etc.) for your situation.
> >
> > If you're having difficulty getting your port committed because you have
> > a construct that is used in many other ports, I think you can ask for
> > portmgr's opinion. They will certainly resolve the issue for you.
> > IMHO, I don't see any problem with what you're doing.
> >
> > If your committer has not responded to you in some number of weeks, you
> > can also ask portmgr to reassign the port back to the pool or to another
> > willing committer.
> >
>
> My committer asked:
>
> > Why is necessary chmod to 755? Why need it?
>
> I answered:
>
> > Because the install-sh script has incorrect permissions and generates an
> error if you don't set them correctly.
>
> The committer submitted my response to another person who wrote:
>
> > I'm sorry that's the wrong way to fix that, the premission problem come
> > from the configure script, run in the same problem a year ago. Check
> > games/wormux-devel there is a fix for the same problem maybe you can
> > take the same way.
>
> I asked for clarification about a month ago. I looked at the port he
> referred to, but I don't see how it applies to my situation. So I stated
> that and asked for help. None has been forthcoming, but I haven't pushed
> it either. I know everyone is busy. I certainly am. And we're all
> volunteers as well. So, I'm not complaining. I just want to understand
> what the right way is to solve this particular problem and get the port
> committed.
>
> I've cc'd both of them as well as portmgr. I'll do whatever I'm told to
> do.
Hi Paul,
I'm sorry, sylivo@ is still on wedding vacation,
his inet access is very limited for this time.
I already wrote to you on 18 DEC after getting
your FW: ...
- - Martin
PS:
portmgr isn't necessarily here.
>
> Paul Schmehl, If it isn't already
> obvious, my opinions are my own
> and not those of my employer.
> **
> WARNING: Check the headers before replying
>
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
>
- --
+---+---+
| PGP: 0xB1E6FCE9 | Jabber : miwi(at)BSDCrew.de |
| Skype : splash_111 | Mail : miwi(at)FreeBSD.org |
+---+---+
| Mess with the Best, Die like the Rest! |
+---+---+
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.12 (FreeBSD)
iEYEARECAAYFAksssq8ACgkQdLJIhLHm/Onf1wCfXrhjUodtlXz4bBdginV4/RW5
9HMAnjC9obmEsQr3/biyilYBoggq5Fud
=DOLu
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
INDEX build failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found Done. make_index: neonpp-0.3_1: no entry for /usr/ports/www/neon26 make_index: neonpp-0.3_1: no entry for /usr/ports/www/neon26 Committers on the hook: beat dougb gerald marcus miwi nemoliu pav wen Most recent CVS update was: U lang/gcc45/Makefile U lang/gcc45/distinfo U ports-mgmt/portmaster/Makefile U ports-mgmt/portmaster/files/portmaster.8 U ports-mgmt/portmaster/files/portmaster.sh.in U x11/gnome2/Makefile ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Need help with a port
I've looked at your port, and FWIW I don't see anything wrong with
your suggested fix. I have attached a patch with some small tweaks to
what you proposed, as well as some changes to the rc.d script.
Regarding the latter:
1. A $FreeBSD$ cvs id is effectively mandatory
2. We prefer that local scripts REQUIRE: LOGIN unless there is a good
reason to run before it
3. Duplicating the documentation in the rc.d script is not desirable.
4. The s#%%RC_SUBR%%#/etc/rc.subr# change will happen soon to all
ports anyway
5. load_rc_config is supposed to come AFTER rcvar
6. I added a required_files for the conf file, since it is included in
command_args
7. It is not necessary or desirable to include $name_flags in
command_args.
Please test this version of the port. If you're satisfied with the
changes I will commit it for you.
Doug
--
Improve the effectiveness of your Internet presence with
a domain name makeover!http://SupersetSolutions.com/
Index: Makefile
===
RCS file: /home/pcvs/ports/security/barnyard2/Makefile,v
retrieving revision 1.1
diff -u -r1.1 Makefile
--- Makefile9 Sep 2009 01:42:43 - 1.1
+++ Makefile19 Dec 2009 08:07:18 -
@@ -6,7 +6,7 @@
#
PORTNAME= barnyard2
-PORTVERSION= 1.6
+PORTVERSION= 1.7
CATEGORIES=security
MASTER_SITES= http://www.securixlive.com/download/barnyard2/
@@ -39,8 +39,10 @@
CONFIGURE_ARGS+= --with-postgresql
.endif
-post-install:
+post-patch:
+ ${CHMOD} 755 ${WRKSRC}/install-sh
+post-install:
.for f in barnyard2.conf
${INSTALL_DATA} ${WRKSRC}/etc/${f} ${PREFIX}/etc/${f}-sample
[ -f ${PREFIX}/etc/${f} ] || \
@@ -48,7 +50,6 @@
.endfor
.if !defined(NOPORTDOCS)
@${MKDIR} ${DOCSDIR}
-# cd ${WRKSRC} && ${INSTALL_DATA} ${DOCS} ${DOCSDIR}
cd ${WRKSRC}/doc && ${INSTALL_DATA} ${PORTDOCS} ${DOCSDIR}
.endif
Index: distinfo
===
RCS file: /home/pcvs/ports/security/barnyard2/distinfo,v
retrieving revision 1.1
diff -u -r1.1 distinfo
--- distinfo9 Sep 2009 01:42:43 - 1.1
+++ distinfo19 Dec 2009 08:07:18 -
@@ -1,3 +1,3 @@
-MD5 (barnyard2-1.6.tar.gz) = fe49fae09f585677af7dda53f3f4bedf
-SHA256 (barnyard2-1.6.tar.gz) =
c8b9b58d48b420634c502d27f21cbdaf42df0205abeb2970f9ee7e114744433b
-SIZE (barnyard2-1.6.tar.gz) = 631471
+MD5 (barnyard2-1.7.tar.gz) = 6801649c45287799354e0a458af737ef
+SHA256 (barnyard2-1.7.tar.gz) =
a9bd56c2887111f3c114e82fc9277ee759a5005374081136e76d950ff390fd1b
+SIZE (barnyard2-1.7.tar.gz) = 652605
Index: files/barnyard2.sh.in
===
RCS file: /home/pcvs/ports/security/barnyard2/files/barnyard2.sh.in,v
retrieving revision 1.1
diff -u -r1.1 barnyard2.sh.in
--- files/barnyard2.sh.in 9 Sep 2009 01:42:44 - 1.1
+++ files/barnyard2.sh.in 19 Dec 2009 08:07:18 -
@@ -1,9 +1,9 @@
#!/bin/sh
#
+# $FreeBSD$
# PROVIDE: barnyard2
-# REQUIRE: DAEMON
-# BEFORE: LOGIN
+# REQUIRE: LOGIN
# KEYWORD: shutdown
# Add the following lines to /etc/rc.conf to enable barnyard2:
@@ -13,59 +13,20 @@
# Default: -D
# barnyard2_conf (str):Barnyard configuration file
# Default: %%PREFIX%%/etc/barnyard2.conf
-#
-# USAGE: barnyard2 [-options]
-#
-# General Options:
-#-? Show this information
-#-c Use configuration file
-#-g Run barnyard gid as group (or gid) after
initialization
-#-m Set umask =
-#-q Quiet. Don't show banner and status report
-#-u Run barnyard uid as user (or uid) after
initialization
-#-v Be verbose
-#-C Read the classification map from
-#-D Run barnyard in background (daemon) mode
-#-G Read the gen-msg map from
-#-LWrite output files in
-#-R Read the reference map from
-#-S Read the sid-msg map from
-#-T Test and report on the current configuration
-#-U Use UTC for timestamps
-#-V Show version and exit
-#
-# Continual Processing Options:
-#-aArchive processed files to
-#-f Use as the base filename pattern
-#-dSpool files from
-#-n Only process new events
-#-w Enable bookmarking using
-#
-# Batch Processing Mode Options:
-#-o Enable batch processing mode
-#
-# Longname options and their corresponding single char version
-# --reference Same as -R
-# --classification Same as -C
-# --gen-msg Same as -G
-# --sid-msg Same as -S
-# --pid-pathSpecify the path for the barnyard PID file
-# --create-pidfileCreate PID file, even when not in Daemon
mode
-# --nolock-pidfile
Re: ioquake3 support more platforms
Dominic Fandrey wrote: > But that's not different for any port. E.g. sysutils/bsdadminscripts is > all mine, I create the distfiles and maintain the port, their is no > guarantee that I don't do evil apart from me being quite certain that > I don't. Mark already pointed out that maintainers and committers actually _do_ have a responsibility to dig into changes, be knowledgeable about upgrades, etc. I agree with his perspective on this. > Why can one assume that an ioquake release is safe? One really cannot. > It's made by the same people who maintain the non-trustworthy SVN. > > What if I created a sourceforge project freebsd-ioquake and published > my distfiles there as ioquake freebsd releases. Would it suddenly > turn trustworthy? The security problems involved in trying to audit a fixed, known set of files are miniscule compared to the problems involved in auditing a set of files that can change on a minute by minute basis. The whole concept of creating a FreeBSD port that checks source files out of a third-party svn repository is anathema to the whole concept of ports security. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover!http://SupersetSolutions.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
