Date: Mon, 24 May 2004 17:47:34 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Alexander Leidinger <Alexander@Leidinger.net>, freebsd-ports@freebsd.org Subject: Re: Third "RFC" on on pkg-data ideas for ports Message-ID: <p06020416bcd81d642885@[128.113.24.47]> In-Reply-To: <p06020414bcd7feb5f782@[128.113.24.47]> References: <p0602040dbcd716257540@[128.113.24.47]> <20040524193815.21b18d80@Magellan.Leidinger.net> <p06020414bcd7feb5f782@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
At 3:46 PM -0400 5/24/04, Garance A Drosihn wrote: >At 7:38 PM +0200 5/24/04, Alexander Leidinger wrote: >> >>ATM you can checkout one (new/updated) port from cvs into >>any non-"ports/" directory and it will work just fine >>(depending on the dependencies of the port). I don't see >>how this is possible with [the above] approach. > >..., I was assuming >that the end-user would still be working in a copy of the >entire ports-collection, so I was just going to download >into ports/Packages. Maybe that isn't the right idea. Actually, the solution is probably pretty simple. Just create a distfiles/Patches directory, and download any missing "ports-collection patches" into that directory, if we can't find them in ports/Patches... -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06020416bcd81d642885>