Re: PostgreSQL 8.x defaults
--On måndag, april 09, 2007 08.36.19 -0500 Craig Boston <[EMAIL PROTECTED]> wrote: I'm not sure of a good solution however. Do you think it would be possible / reasonable for the periodic job to check if the user has set postgresql_enable and do nothing if it is not enabled? That is certainly a good idea! ;-) /Palle ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Printing with Acrobat Reader
Hi,
I've configured Adobe Reader to use "/usr/bin/lpr -Plaser"
for printing ("laser" is the name of the printing queue for
my PostScript printer). But when I try to print a document,
I get the error message "/usr/bin/lpr not found".
Obviously Adobe Reader tries to locate the given binary in
/compat/linux. When I copy /usr/bin/lpr (FreeBSD binary)
to /compat/linux/usr/bin, printing from Adobe Reader works
fine.
Now I have a few questions ... :-)
First, copying the FreeBSD binary to /compat/linux seems
like a dirty hack. Is there a better way to solve the
problem?
Second, if there's no better way, then shouldn't the port
already copy the lpr binary upon install (and remove it
upon deinstall), so printing works out of the box? Or
install a small shellscript wrapper in /compat/linux that
calls /usr/bin/lpr. (Or at least add a message to the
FreeBSD port to hint users that they need to copy the
binary.)
Best regards
Oliver
--
Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M.
Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung:
secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün-
chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart
FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd
"The scanf() function is a large and complex beast that often does
something almost but not quite entirely unlike what you desired."
-- Chris Torek
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: qemu: kqemu not compiled?
Juergen Lock wrote: On Mon, Apr 09, 2007 at 09:51:50PM +0200, Ivan Voras wrote: Good advice, except that qemu-system-x86_64 locks up the machine hard, no autoreboot. Ouch! But only with kqemu I guess? Also, whats your guest and args to qemu-system-x86_64? Yes, it works without kqemu loaded. My guest is FreeBSD 6.2-R AMD64, I'm running it with: qemu-system-x86_64 -hda disk -cdrom 6.2-RELEASE-i386-disc1.iso -boot d -m 512 I've now tried both i386 and AMD64 guests, and both panic with kqemu, before kernel gets loaded. signature.asc Description: OpenPGP digital signature
Re: qemu: kqemu not compiled?
RW wrote: Would you expect to able to run kqemu, when the architecture is different between the host and guest? Yes, I'd expect it to translate and fixup the instructions. (Why? "VMware does it" :) ). The point of kqemu is that some instructions in the guest can be run natively on the host cpu. Unless there's some special support in kqemu for switching backwards and forwards between 32 and 64 mode, that's not going to work. signature.asc Description: OpenPGP digital signature
Re: parallel builds revisited
Benjamin Lutz píše v út 10. 04. 2007 v 04:52 +0200: > Some time ago, after buying a Core 2 Duo system, I've become interested > in doing something about the inherent single-threadedness of the ports. > Even though I have a dualcore machine, ports builds only ever use one > core. I started thinking about various approaches to introduce > parallelism to ports builds and wrote down my thoughts here: > http://marc.info/?l=freebsd-ports&m=116124997126657&w=2 I have same thoughts, and I wrote about it on Project Ideas page. That text materialized into a Summer of Code proposal, which is most probably going to get funded. So stay tuned. However, the proposal concentrates mainly on allowing several ports to build in parallel. > Well, since then I've tinkered with various approaches. I concentrated > on using make's -j feature. After adding the flag to the gmake > invocation in bsd.port.mk, I quickly noticed that some ports can take > advantage of the flag and thus build much more quickly (eg, all the KDE > ports), Because they use gmake > others are still single-threaded (X.org), Because they use imake > but of course there are also ports that fail to build (Openoffice.org). Now that means nothing :) > This means that a per-port switch is required. Yes, a whitelist approach looks best. > 3) Save this to /usr/local/etc/parallel_builds.conf: > http://www.maxlor.com/temp/parallel_builds.conf . > This is a list of ports as stored in PKGORIGIN, or as > pkg_info -o reports them. I was thinking about having it embedded in every port's Makefile directly, instead. Something like USE_MAKE_JOBS= 2 > So now I would like to invite you test, comment, or simply philosophize > on these changes. I have great interest in this development. This is a highly desirable feature to have. -- Pav Lucistnik <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Linux is a happy free-for-all chaos. signature.asc Description: Toto je digitálně podepsaná část zprávy
OPTIONS changes
Am I correct in assuming that with the new changes default OPTIONS no longer need to be written as: .if !defined(WITHOUT_FOO) Will pointyhat deal correctly with: .if defined(WITH_FOO) if it defaults to "on"? Thanks, Beech --- Beech Rintoul - Port Maintainer - [EMAIL PROTECTED] /"\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://www.freebsd.org X - NO Word docs in e-mail | Latest Release: / \ - http://www.freebsd.org/releases/6.2R/announce.html --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
syslog-ng2 conf path default changed; pkg-plist out of date
Okay...who broke this: The path in the binary to the default config file has changed but the pkg-list hasn't and aside from the 2.0.2 patch level bump I dont see where else it came from: [EMAIL PROTECTED] ~]$ strings /usr/local/sbin/syslog-ng |egrep "\.conf" -f , --cfgfile=Set config file name, default=/usr/local/etc/syslog-ng.conf /usr/local/etc/syslog-ng.conf [EMAIL PROTECTED] /usr/local/cf]$ sudo bash -x /usr/local/etc/rc.d/syslog-ng restart [...snip...] ++ /usr/local/sbin/syslog-ng -p /var/run/syslog.pid Error opening configuration file; filename='/usr/local/etc/syslog-ng.conf', error='No such file or directory (2)' The work-around for the mean time is: syslog_ng_flags="-f /usr/local/etc/syslog-ng/syslog-ng.conf" I need to see a CVS changelog of certain files, but Balavid doesn't have a cvsweb, viewvc, etc. or public CVS archive? l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA) http://www.spiritual-machines.org/ "...from back in the heady days when "helpdesk" meant nothing, "diskquota" meant everything, and lives could be bought and sold for a couple of pages of laser printout - and frequently were." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: OPTIONS changes
Beech Rintoul píše v út 10. 04. 2007 v 10:23 -0800: > Am I correct in assuming that with the new changes default OPTIONS no > longer need to be written as: > > .if !defined(WITHOUT_FOO) > > Will pointyhat deal correctly with: > > .if defined(WITH_FOO) if it defaults to "on"? That's what we think. -- Pav Lucistnik <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> In fact, the GAH is a very powerful and secretive organization whose single weakness is its lack of existance. - rec.games.roguelike.angband signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: qemu: kqemu not compiled?
Ivan Voras wrote: > Juergen Lock wrote: >> On Mon, Apr 09, 2007 at 09:51:50PM +0200, Ivan Voras wrote: > >>> Good advice, except that qemu-system-x86_64 locks up the machine hard, >>> no autoreboot. >> >> Ouch! But only with kqemu I guess? Also, whats your guest and args >> to qemu-system-x86_64? > > Yes, it works without kqemu loaded. My guest is FreeBSD 6.2-R AMD64, I'm > running it with: > > qemu-system-x86_64 -hda disk -cdrom 6.2-RELEASE-i386-disc1.iso -boot d > -m 512 > > I've now tried both i386 and AMD64 guests, and both panic with kqemu, > before kernel gets loaded. Forgot to mention - the host is SMP. signature.asc Description: OpenPGP digital signature
smtp-auth problem
I just setup smtp-auth for relaying, using the instructions at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/smtp-auth.html. Everything went well. However, people connecting get "454 4.3.3 tls not available after start" and in /var/log/maillog i see "[ip] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4" Also - receiving "OTP unavailable because can't read/write key database /etc/opiekeys" twice in /var/log/messages Hmm.. thoughts? Thank you! chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Fetchmail 6.3.8
Jack Raats wrote: > Fetchmail 6.3.8 cann't be fetched from the server. > Thanks for your time Fixed, thanks for the report! -- Best regards / Viele Grüße, [EMAIL PROTECTED] Simon Barner[EMAIL PROTECTED] pgpCU5FwHQN3C.pgp Description: PGP signature
smtp-auth problem
Hope this is the right list. If not, please forward and cc: me, as I am not subscribed. Thanks so much. I just setup smtp-auth for relaying, using the instructions at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/smtp-auth.html. Everything went well. However, people connecting get "454 4.3.3 tls not available after start" and in /var/log/maillog i see "[ip] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4" Also - receiving "OTP unavailable because can't read/write key database /etc/opiekeys" twice in /var/log/messages Hmm.. thoughts? Thank you! chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: qemu: kqemu not compiled?
In article <[EMAIL PROTECTED]> you write: >-=-=-=-=-=- > >Juergen Lock wrote: >> On Mon, Apr 09, 2007 at 09:51:50PM +0200, Ivan Voras wrote: > >>> Good advice, except that qemu-system-x86_64 locks up the machine hard, >>> no autoreboot. >> >> Ouch! But only with kqemu I guess? Also, whats your guest and args >> to qemu-system-x86_64? > >Yes, it works without kqemu loaded. My guest is FreeBSD 6.2-R AMD64, I'm >running it with: > >qemu-system-x86_64 -hda disk -cdrom 6.2-RELEASE-i386-disc1.iso -boot d >-m 512 -m 512 ? Hmm did you increase kern.maxdsiz for that? Since the default is 512M, and qemu needs memory for itself too... (tunable in loader.conf.) Or, failing that, try smaller -m args, like 256. > >I've now tried both i386 and AMD64 guests, and both panic with kqemu, >before kernel gets loaded. Oh, panic, not lockup? Can you get a backtrace? (see http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html , i.e. do a script(1) log of `bt' in kgdb.) Juergen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: qemu: kqemu not compiled?
In article <[EMAIL PROTECTED]> you write: >-=-=-=-=-=- > >Ivan Voras wrote: >> Juergen Lock wrote: >>> On Mon, Apr 09, 2007 at 09:51:50PM +0200, Ivan Voras wrote: >> Good advice, except that qemu-system-x86_64 locks up the machine hard, no autoreboot. >>> >>> Ouch! But only with kqemu I guess? Also, whats your guest and args >>> to qemu-system-x86_64? >> >> Yes, it works without kqemu loaded. My guest is FreeBSD 6.2-R AMD64, I'm >> running it with: >> >> qemu-system-x86_64 -hda disk -cdrom 6.2-RELEASE-i386-disc1.iso -boot d >> -m 512 >> >> I've now tried both i386 and AMD64 guests, and both panic with kqemu, >> before kernel gets loaded. > >Forgot to mention - the host is SMP. Ok in that case you might also want to try an up kernel to see if its an smp problem. Juergen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: qemu: kqemu not compiled?
Juergen Lock wrote: >> qemu-system-x86_64 -hda disk -cdrom 6.2-RELEASE-i386-disc1.iso -boot d >> -m 512 > > -m 512 ? Hmm did you increase kern.maxdsiz for that? Since the > default is 512M, and qemu needs memory for itself too... (tunable > in loader.conf.) Or, failing that, try smaller -m args, like 256. Hmmm. But does the kqemu allocate the memory or the qemu? I've seen big qemu processes, so I conclude that qemu allocates this memory. But you're right - this may be something to try. >> I've now tried both i386 and AMD64 guests, and both panic with kqemu, >> before kernel gets loaded. > > Oh, panic, not lockup? Can you get a backtrace? (see Sorry, yes, lockup. Always lockup with qemu. signature.asc Description: OpenPGP digital signature
asmail 2.1, FreeBSD port mail/asmail
Hi all,
another release of asmail (2.1) was published recently. Like last time,
I prepared a little patch to update the port. I tested on
6.1-RELEASE-p10 (amd64), 5.4-RELEASE-p9 (i386) and 4.11-RELEASE-p25 (i386).
The 4.11 has no socklen_t, so this will be replaced with int, depending
on OSVERSION.
Could you do me a favour and commit this?
I'd volunteer to maintain this port but unfortunately I'll lose access
to the 6.x and 5.x boxes this week :-(
Cheers,
Martin
diff -ru asmail.orig/Makefile asmail/Makefile
--- asmail.orig/MakefileTue Apr 10 21:42:50 2007
+++ asmail/Makefile Tue Apr 10 21:48:13 2007
@@ -6,7 +6,7 @@
#
PORTNAME= asmail
-PORTVERSION= 2.0
+PORTVERSION= 2.1
CATEGORIES=mail afterstep
MASTER_SITES= http://www.tigr.net/afterstep/download/asmail/
@@ -29,6 +29,8 @@
CPPFLAGS+= ${PTHREAD_CFLAGS}
LDFLAGS+= ${PTHREAD_LIBS} -lssl -lcrypto
+.include
+
post-patch:
@${REINPLACE_CMD} -e 's|-lpthread|${PTHREAD_LIBS}|g ; \
s|machine/soundcard|sys/soundcard|g' ${WRKSRC}/configure
@@ -37,6 +39,11 @@
@${REINPLACE_CMD} -e \
's|/usr/local|${PREFIX}|g' ${WRKSRC}/asmailrc.sample
+.if ${OSVERSION} < 50
+ @${REINPLACE_CMD} -e 's|socklen_t|int|g' ${WRKSRC}/socklib.h
+.endif
+
+
post-install:
.if !defined(NOPORTDOCS)
@${MKDIR} ${DOCSDIR}
@@ -45,4 +52,4 @@
${INSTALL_DATA} ${WRKSRC}/asmailrc.sample ${EXAMPLESDIR}
.endif
-.include
+.include
diff -ru asmail.orig/distinfo asmail/distinfo
--- asmail.orig/distinfoTue Apr 10 21:42:50 2007
+++ asmail/distinfo Tue Apr 10 21:33:58 2007
@@ -1,3 +1,3 @@
-MD5 (asmail-2.0.tar.gz) = 58873242a953f3b4fbbe6cf517f3a51a
-SHA1 (asmail-2.0.tar.gz) = d54d00d744dce674007bb96a6772129ada2e1980
-SIZE (asmail-2.0.tar.gz) = 270924
+MD5 (asmail-2.1.tar.gz) = 10d1460353f5773c8d211003a07312df
+SHA256 (asmail-2.1.tar.gz) =
9b20aff43d61511e9c24af5603a546e3709bad35c769074e2b66d818f33e8191
+SIZE (asmail-2.1.tar.gz) = 271164
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [netops] Re: [syslog-ng] syslog-ng2 conf path default changed; pkg-plist out of date
On Tue, 2007-04-10 at 22:33 +0200, Balazs Scheidler wrote: > be sensitive a bit, but starting a question with "who broke this?" and Sorry. So where is public CVS? ~BAS -- Brian A. Seklecki <[EMAIL PROTECTED]> Collaborative Fusion, Inc. IMPORTANT: This message contains confidential information and is intended only for the individual named. If the reader of this message is not an intended recipient (or the individual responsible for the delivery of this message to an intended recipient), please be advised that any re-use, dissemination, distribution or copying of this message is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [syslog-ng] syslog-ng2 conf path default changed; pkg-plist out of date
On Tue, 2007-04-10 at 14:01 -0400, Brian A. Seklecki wrote: > Okay...who broke this: The path in the binary to the default config file > has changed but the pkg-list hasn't and aside from the 2.0.2 patch level > bump I dont see where else it came from: This was changed between 1.6.x and 2.0.x, as it is not 'nice' to hardwire configure subdirectories into the configure script. Instead packagers need to override --sysconfdir configure option. So it is not broken, it was an intended change. A lot of other differences were also introduced in from 1.6.x->2.0.0, so I thought it would be ok to change it. and 2.0.3 introduces the use of "localstatedir" too. This defaults to $prefix/var which should be redefined to /var/lib/syslog-ng. Software do change, packaging/compile scripts need to be adapted from time to time. And one minor note about your message: because of the tone I played with the idea of _not replying_, but at the end I decided to respond. I might be sensitive a bit, but starting a question with "who broke this?" and mistyping the name of the developer as "Balavid" sounds a bit rude to me. -- Bazsi ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: ruby18-xmpp4r-0.3
On Sat, 7 Apr 2007 20:59:09 +0200 "Vladimir Horak" <[EMAIL PROTECTED]> mentioned: > Hello! > > I discover problem with ruby18-xmpp4r-0.3 and new ruby-1.8.6,1. > The problem apply to Digest::MD5 (see > http://svn.ruby-lang.org/repos/ruby/tags/v1_8_6/NEWS). > > This solve it: > > sasl.rb: > 44c44 > < Digest::MD5.new(Time.new.to_f.to_s).hexdigest > --- > > Digest::MD5.hexdigest(Time.new.to_f.to_s) > I could commit this if maintainer doesn't mind. -- Stanislav Sedov ST4096-RIPE pgpFdwUOKThGS.pgp Description: PGP signature
[Fwd: Re: ports/111462: syslog-ng2 default configuration file path]
ports/111462 filed. Have a great evening all*
--
$ diff -u 2.0.0/syslog-ng.spec.bb 2.0.2/syslog-ng.spec.bb |grep -i conf
-./configure --prefix=/ --mandir=/usr/share/man
--infodir=/usr/share/info \
- --sysconfdir=/etc
+./configure --prefix=%{prefix} --mandir=%{_mandir} \
+ --infodir=%{prefix}/share/info + --sysconfdir=/etc/syslog-ng
--
Brian A. Seklecki <[EMAIL PROTECTED]>
Collaborative Fusion, Inc.
IMPORTANT: This message contains confidential information and is intended only
for the individual named. If the reader of this message is not an intended
recipient (or the individual responsible for the delivery of this message to an
intended recipient), please be advised that any re-use, dissemination,
distribution or copying of this message is prohibited. Please notify the
sender immediately by e-mail if you have received this e-mail by mistake and
delete this e-mail from your system.
--- Begin Message ---
Thank you very much for your problem report.
It has the internal identification `ports/111462'.
The individual assigned to look at your
report is: freebsd-ports-bugs.
You can access the state of your problem report at any time
via this link:
http://www.freebsd.org/cgi/query-pr.cgi?pr=111462
>Category: ports
>Responsible:freebsd-ports-bugs
>Synopsis: syslog-ng2 default configuration file path
>Arrival-Date: Tue Apr 10 22:40:01 GMT 2007
--- End Message ---
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: qemu: kqemu not compiled?
On Tue, Apr 10, 2007 at 10:09:20PM +0200, Ivan Voras wrote: > Juergen Lock wrote: > > >> qemu-system-x86_64 -hda disk -cdrom 6.2-RELEASE-i386-disc1.iso -boot d > >> -m 512 > > > > -m 512 ? Hmm did you increase kern.maxdsiz for that? Since the > > default is 512M, and qemu needs memory for itself too... (tunable > > in loader.conf.) Or, failing that, try smaller -m args, like 256. > > Hmmm. But does the kqemu allocate the memory or the qemu? I've seen big > qemu processes, so I conclude that qemu allocates this memory. But > you're right - this may be something to try. Well default max datasize limit on FreeBSD is 512M, trying to allocate more should fail, but might do worse in this case... (even when it would be a bug.) Juergen ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: netdisco-0.94
On Mon, Apr 09, 2007 at 11:43:44AM -0700, John Killian wrote: > > Hi Shaun, > > Wondering if there are any plans to update the NETDISCO port to 0.95 > which came out last November? > > Thank you for maintaining this port. > Yes, I will update the port when I have a chance. There is a PR in GNATS with an update if you desperately need the newer version - although I haven't looked at the patch yet. Shaun -- Shaun Amott // PGP: 0x6B387A9A "A foolish consistency is the hobgoblin of little minds." - Ralph Waldo Emerson ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Printing with Acrobat Reader
Oliver Fromme wrote: First, copying the FreeBSD binary to /compat/linux seems like a dirty hack. Is there a better way to solve the problem? I don't know if this is a better way but here's the wrapper that I've been using to coerce printing with acro7 and my printer at lpr -Pps #!/bin/sh #needed to make linux acroread7 work export LD_LIBRARY_PATH=/usr/compat/usr/X11R6/lib:LD_LIBRARY_PATH acroread "$1" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: local ports
Vulpes Velox wrote: > I was just wondering what any one else thought of the idea of adding > a local directory to the ports tree and to the .cvsignore. This would > be a directory for users to put local custom ports. There's nothing to stop you from creating /usr/ports/local right now and just using it. You don't need a .cvsignore if you are using cvsup/csup, they ignore files that aren't in the cvs repo anyways. Of course if you are using portsnap that might be a different story, not sure how it handles updates... -- Thanks, Josh Paetzel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: local ports
On Tue, 10 Apr 2007 21:15:04 -0500 Josh Paetzel <[EMAIL PROTECTED]> wrote: > Vulpes Velox wrote: > > I was just wondering what any one else thought of the idea of > > adding a local directory to the ports tree and to the .cvsignore. > > This would be a directory for users to put local custom ports. > > There's nothing to stop you from creating /usr/ports/local right > now and just using it. You don't need a .cvsignore if you are > using cvsup/csup, they ignore files that aren't in the cvs repo > anyways. Of course if you are using portsnap that might be a > different story, not sure how it handles updates... I know. :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: local ports
On Tue, Apr 10, 2007 at 09:15:04PM -0500, Josh Paetzel wrote: > Vulpes Velox wrote: > > I was just wondering what any one else thought of the idea of adding > > a local directory to the ports tree and to the .cvsignore. This would > > be a directory for users to put local custom ports. > > There's nothing to stop you from creating /usr/ports/local right now > and just using it. You don't need a .cvsignore if you are using > cvsup/csup, they ignore files that aren't in the cvs repo anyways. > Of course if you are using portsnap that might be a different story, > not sure how it handles updates... Just fine. The author even added the -l option at my request so you can still use portsnap's INDEX updating stuff. You just need to collect the results of "make describe" in your local ports and pass the file containing it as the argument to -l when updating. I'm using it at work with a wrapper script that updates my local ports via subversion and updates official ports via portsnap on one go. - -Brooks pgptpsTaG6XHh.pgp Description: PGP signature
problem in compiling by gfortran
Hello, I cannot build biology/platon on my hosts. Precise report has been sent to PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=108105 , but no one reproduce the same trouble. I confirmed that one host with 7-current can build this, and that no warning messages are printed. But other hosts of 6-stable prints many warnings, as reported with PR. I want to know the reason of these warnings. But I am not familier with recent fortran, I cannot understand them. Please teach me, and if possible, solve this problem. --- Tsurutani Naoki [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
