Date: Thu, 06 Apr 2006 21:03:55 +1000 From: freebsd-questions@auscert.org.au To: freebsd-questions@freebsd.org Subject: Re: How to handle 'local' ports/packages? Message-ID: <200604061103.k36B3teN014554@app.auscert.org.au> In-Reply-To: Your message of "Thu, 06 Apr 2006 01:47:28 %2B0100." <200604060147.30726.list-freebsd-2004@morbius.sent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Wednesday 05 April 2006 01:35, freebsd-questions@auscert.org.au wrote: > > > to the +CONTENTS file for the package, but then portmanager complains that > > it is nonexistent and won't complete 'portmanager -s'. To make matters > > more awkward, this package is built from a closed-source binary > > distribution and thus can't be properly ported, so I can't set it up > > properly. > > A port does not have to be built from source, there are several (maybe many) > closed-source packages in the ports-tree, for example: > > archivers/rar > mail/mulberry > x11/nvidia-driver Ok, that's fine, but how can I have a port on my system that isn't in the ports tree available to the world? I mean, won't anything I add to my local tree be deleted by cvsup'ing? joel -- Joel Hatton -- Infrastructure Manager | Hotline: +61 7 3365 4417 AusCERT - Australia's national CERT | Fax: +61 7 3365 7031 The University of Queensland | WWW: www.auscert.org.au Qld 4072 Australia | Email: auscert@auscert.org.au
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200604061103.k36B3teN014554>