Date: Thu, 25 May 2006 17:23:18 +0400 From: Dmitry Marakasov <amdmi3@mail.ru> To: Peter Jeremy <peterjeremy@optushome.com.au> Cc: freebsd-ports@FreeBSD.org Subject: Re: [FreeBSD-Announce] Volunteers needed to help maintain ports Message-ID: <20060525132318.GC15332@hades.panopticon> In-Reply-To: <20060525121240.GC724@turion.vk2pj.dyndns.org> References: <20060524233036.GA91627@xor.obsecurity.org> <20060525113949.GA14925@hades.panopticon> <20060525121240.GC724@turion.vk2pj.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
* Peter Jeremy (peterjeremy@optushome.com.au) wrote: > On Thu, 2006-May-25 15:39:49 +0400, Dmitry Marakasov wrote: > >2) Software with new versions released frequently. The port has no > >maintainer, but still it's updated by `by-passers' regularly, so it's > >at latest version. > One problem with these sort of drive-by updates is that they are > likely to break dependency trees. One recent example is that > lang/slib was updated to version 3a3 but neither lang/slib-gauche nor > lang/slib-guile were updated - thus breaking both of them. The other > problem is that the update has probably only been checked on one > platform so whilst the update may compile on other architectures, it > might fail to run and this is less likely to be noticed/fixed. Yes, of course maintainers tend to be more aware of depends and caveats of their ports and give their patches more testing, though being maintainer doesn't intend that you have park of all possible architectures, so mistakes can happen anyway. > >3) Ports that actually need a maintainer. This is small percentage of > >currently `unmaintained' ports. I think most of these are in specific > >categories like biology, science, finance. > IMHO, some of the ports in security should be managed by the security > team rather than ports@. That's good idea. -- Best regards, Dmitry mailto:amdmi3@mail.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060525132318.GC15332>