Re: [gentoo-dev] RFC: leechcraft.eclass
* Alex Alexander schrieb am 22.07.11 um 13:30 Uhr: > On Fri, Jul 22, 2011 at 14:21, Marc Schiffbauer wrote: > > Am Freitag, 22. Juli 2011, 14:50:06 schrieb Maxim Koltsov: > >> Hi devs, > >> I'm about to add Leechcraft modular internet client to tree. It has 32 > >> packages and uses it's own eclass. Please review it and allow me to > >> commit it to the tree. > >> Also i'd want to ask: is it woth to add new category (e.g. > >> leechcraft-plugins) to simplify managing leechcraft ebuilds. And the > >> last question: is it good to add versions for all ebuilds too? > > > > IMO live ebuilds should only be held in an overlay. > > > > -Marc > > versions are nice, but they typically require more time and > effort to maintain. I'd recommend adding them only if you are willing > to do the work. Sometimes ebuilds are useful as a way to prepare > for the next release. Yes, but the big drawback is that you do not have any checksums of the source. So if for example an upstream source code gets exploited you will never notice until the trojan or whatever got in there will do something. Sure this can happen with normal tarballs too, but is much more unlikely and can only happen if the source is already bad at the time of "repoman manifest". -Marc -- 8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134 pgpiMgjqTV4DQ.pgp Description: PGP signature
Re: [gentoo-dev] RFC: leechcraft.eclass
2011/7/22 Chí-Thanh Christopher Nguyễn : > But I do think it is > good to have live ebuilds in portage, especially for fast moving > applications. I think they can be useful for any application as long as they're maintained. I can see the value of the QA policy that they must be masked, but I don't see value in forcing them out of the tree. I think the key is that we want the tree to work - if it works then it belongs. The ability to seamlessly support live builds is one of Gentoo's distinctive features - since we're already a bit of a niche we should embrace this. Rich
Re: [gentoo-dev] RFC: leechcraft.eclass
Maxim Koltsov schrieb: > Also i'd want to ask: is it woth to add new category (e.g. > leechcraft-plugins) to simplify managing leechcraft ebuilds. And the > last question: is it good to add versions for all ebuilds too? > I don't think there is a need for a new category. But I do think it is good to have live ebuilds in portage, especially for fast moving applications. If you are very close to upstream (as it seems to be) then you can submit patches directly there which makes maintaining the live ebuilds easier. Best regards, Chí-Thanh Christopher Nguyen
Re: [gentoo-dev] RFC: leechcraft.eclass
On Fri, Jul 22, 2011 at 14:21, Marc Schiffbauer wrote: > Am Freitag, 22. Juli 2011, 14:50:06 schrieb Maxim Koltsov: >> Hi devs, >> I'm about to add Leechcraft modular internet client to tree. It has 32 >> packages and uses it's own eclass. Please review it and allow me to >> commit it to the tree. >> Also i'd want to ask: is it woth to add new category (e.g. >> leechcraft-plugins) to simplify managing leechcraft ebuilds. And the >> last question: is it good to add versions for all ebuilds too? > > IMO live ebuilds should only be held in an overlay. > > -Marc versions are nice, but they typically require more time and effort to maintain. I'd recommend adding them only if you are willing to do the work. Sometimes ebuilds are useful as a way to prepare for the next release. -- Alex Alexander | wired + Gentoo Linux Developer ++ www.linuxized.com
Re: [gentoo-dev] RFC: leechcraft.eclass
Am Freitag, 22. Juli 2011, 14:50:06 schrieb Maxim Koltsov: > Hi devs, > I'm about to add Leechcraft modular internet client to tree. It has 32 > packages and uses it's own eclass. Please review it and allow me to > commit it to the tree. > Also i'd want to ask: is it woth to add new category (e.g. > leechcraft-plugins) to simplify managing leechcraft ebuilds. And the > last question: is it good to add versions for all ebuilds too? IMO live ebuilds should only be held in an overlay. -Marc
[gentoo-dev] RFC: leechcraft.eclass
Hi devs, I'm about to add Leechcraft modular internet client to tree. It has 32 packages and uses it's own eclass. Please review it and allow me to commit it to the tree. Also i'd want to ask: is it woth to add new category (e.g. leechcraft-plugins) to simplify managing leechcraft ebuilds. And the last question: is it good to add versions for all ebuilds too?