Date: Mon, 23 Feb 2009 19:15:35 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: perryh@pluto.rain.com Cc: freebsd-questions@freebsd.org Subject: Re: hi Message-ID: <87mycd847c.fsf@kobe.laptop> In-Reply-To: <49a20440.oqh9j8d04xp6dYo8%perryh@pluto.rain.com> (perryh@pluto.rain.com's message of "Sun, 22 Feb 2009 18:04:48 -0800") References: <9ef7e7380902220154t74657d52uc9497c77672b79f8@mail.gmail.com> <9a52b1190902220711u65e38320t97ca56547bef246d@mail.gmail.com> <87ljryccm0.fsf@kobe.laptop> <49a20440.oqh9j8d04xp6dYo8%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 22 Feb 2009 18:04:48 -0800, perryh@pluto.rain.com wrote: >Giorgos Keramidas wrote: >> You can always check out ... from a date before its removal from >> the ports/ tree ... If you need help with maintaining a local >> copy of the relevant ports ... let me know and I'll write a short >> mini-guide for checking out the ports before their removal and >> building them as local ports. > > This sounds as if it would make a good Handbook section. Documenting such local 'hacks' in the Handbook is a bit like rubber stamping them with the official 'recommended by FreeBSD' seal of approval. I am not sure I would like that a lot. Serious security problems may exist in stale, unmaintained ports. It would be a bit bad to make it sound like the entire FreeBSD project approves and even recommends this sort of thing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?87mycd847c.fsf>