Re: [gentoo-dev] Re: Project Sunrise thread -- a try of clarification
On Fri, Jun 09, 2006 at 02:04:57PM +0200, Stefan Schweizer wrote: svn co http://overlays.gentoo.org/svn/proj/sunrise/category/application; emerge application As long as it's made for pulling single ebuilds (and their support files), i think it's really helpfull. It's exactly the same as downloading single ebuilds from Bugzilla just without the pain of using bugzilla for it. While Bugzilla is fine for handling bugs, i think it's annoying to use for maintaining and downloading ebuilds. The danger of people breaking something is exactly the same though. I don't see a difference between downloading an ebuild with bugzilla and fetching them with svn. What i would fear is a full overlay with eclasses and many other things the user didn't cherry pick. I would mostly like a method to easily add external ebuilds to my own overlay. When that source allows people to maintain their ebuilds in a simple way, it's also better. Raising the annoyance bar for handling ebuilds doesn't increase their quality. Christian -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Project Sunrise thread -- a try of clarification
On Sun, Jun 11, 2006 at 03:42:19PM +0200, Christian Birchinger wrote: On Fri, Jun 09, 2006 at 02:04:57PM +0200, Stefan Schweizer wrote: svn co http://overlays.gentoo.org/svn/proj/sunrise/category/application; emerge application As long as it's made for pulling single ebuilds (and their support files), i think it's really helpfull. The way SVN works you can just as easily do svn co http://overlays.gentoo.org/svn/proj/sunrise/; and get the full repository - so no, this is not limited to pulling single ebuilds. ./Brix -- Henrik Brix Andersen [EMAIL PROTECTED] Gentoo Metadistribution | Mobile computing herd pgpdMipiLWjnS.pgp Description: PGP signature
[gentoo-dev] Re: Project Sunrise thread -- a try of clarification
Carsten Lohrke wrote: You should at least make it visible in bold letters on the overlay.g.o front page, what the conditions of each overlay are and which [EMAIL PROTECTED] address bugs have to be assigned to. Please, do not assume our users being stupid. They know that they are using an ebuild from the sunrise overlay with zero support. They deliberately typed svn co http://overlays.gentoo.org/svn/proj/sunrise/category/application; emerge application And also there are only applications from maintainer-wanted or maintainer-needed allowed in the overlay. Because packages are not supposed to overwrite files from other ebuilds it is unlikely that they can cause any damage to applications that have not been directly installed from the overlay. Also some warning that an overlay may break the tree or fubar the users system That is not the intention of the overlay. Everyone can help fixing breakage, it is not like with the current tree, where you have apps broken for a few days, weeks or even months because the maintainer is unreachable. With fixes (by users) spread all over bugzilla. It is designed to be more open and more easily fixable. -Stefan -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Project Sunrise thread -- a try of clarification
On Friday 09 June 2006 14:04, Stefan Schweizer wrote: Please, do not assume our users being stupid. They know that they are using an ebuild from the sunrise overlay with zero support. They deliberately typed You have said stupid, not me. Some won't care enough, I'm quite sure about that. We had such invalid bug reports occasionally in the past and I expect this to happen more often, the easier and more common dealing with overlays becomes. Regarding zero support: Making this abslutely clear is what I miss looking at overlays.g.o. svn co http://overlays.gentoo.org/svn/proj/sunrise/category/application; emerge application And also there are only applications from maintainer-wanted or maintainer-needed allowed in the overlay. Because packages are not supposed to overwrite files from other ebuilds it is unlikely that they can cause any damage to applications that have not been directly installed from the overlay. maintainer-needed is imho not acceptable at all, as any dev trying to clean up bugs, won't know if a bug report comes from a user of the main tree ebuild or from your overlay. Also some warning that an overlay may break the tree or fubar the users system That is not the intention of the overlay. If it were intended, it would be malicious. Even if not intended, it doesn't mean tree breakages won't happen. Some dev may change an eclass, without taking overlay ebuilds into account (and he doesn't have to), but the change may break all ebuilds inheriting the eclass in an overlay, leaving all the users of the overlay with a broken tree. And to make that clear: Eclasses in overlays are only sort of acceptable, when the same team handles the eclass in the the main tree, as eclasses in overlays hide the main tree eclasses. Carsten pgpU7l3V10Wea.pgp Description: PGP signature
Re: [gentoo-dev] Re: Project Sunrise thread -- a try of clarification
Am Freitag, 9. Juni 2006 14:04 schrieb Stefan Schweizer: And also there are only applications from maintainer-wanted or maintainer-needed allowed in the overlay. Because packages are not supposed to overwrite files from other ebuilds it is unlikely that they can cause any damage to applications that have not been directly installed from the overlay. Only when you got FEATURES=collision-protect. Danny -- Danny van Dyk [EMAIL PROTECTED] Gentoo/AMD64 Project, Gentoo Scientific Project -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Project Sunrise thread -- a try of clarification
Am Freitag, 9. Juni 2006 14:04 schrieb Stefan Schweizer: And also there are only applications from maintainer-wanted or maintainer-needed allowed in the overlay. Because packages are not supposed to overwrite files from other ebuilds it is unlikely that they can cause any damage to applications that have not been directly installed from the overlay. That is only true, if you have enabled FEATURES=collision-protect. Danny -- Danny van Dyk [EMAIL PROTECTED] Gentoo/AMD64 Project, Gentoo Scientific Project -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Project Sunrise thread -- a try of clarification
Am Freitag, 9. Juni 2006 14:04 schrieb Stefan Schweizer: And also there are only applications from maintainer-wanted or maintainer-needed allowed in the overlay. Because packages are not supposed to overwrite files from other ebuilds it is unlikely that they can cause any damage to applications that have not been directly installed from the overlay. Only when you have FEATURES=collision-protect. Danny -- Danny van Dyk [EMAIL PROTECTED] Gentoo/AMD64 Project, Gentoo Scientific Project -- gentoo-dev@gentoo.org mailing list
Re: [gentoo-dev] Re: Project Sunrise thread -- a try of clarification
On Fri, 2006-06-09 at 14:04 +0200, Stefan Schweizer wrote: Carsten Lohrke wrote: You should at least make it visible in bold letters on the overlay.g.o front page, what the conditions of each overlay are and which [EMAIL PROTECTED] address bugs have to be assigned to. Please, do not assume our users being stupid. They know that they are using an ebuild from the sunrise overlay with zero support. They deliberately typed svn co http://overlays.gentoo.org/svn/proj/sunrise/category/application; emerge application Umm... and what if they checkout the entire repository and get something they weren't expecting? I love how you simply just dismiss this possibility as something that either can't happen, or something that won't happen because the users will know what they're doing when they use this overlay. And also there are only applications from maintainer-wanted or maintainer-needed allowed in the overlay. Because packages are not supposed to overwrite files from other ebuilds it is unlikely that they can cause any damage to applications that have not been directly installed from the overlay. Hahahahahahahahahahahaha!! Oh wait... Are you serious? What if it is a library? What if it is an alternative to a library already in the tree? Hrrrmn... plot thickens. Also some warning that an overlay may break the tree or fubar the users system That is not the intention of the overlay. Everyone can help fixing breakage, it is not like with the current tree, where you have apps broken for a few days, weeks or even months because the maintainer is unreachable. With fixes (by users) spread all over bugzilla. Everyone that you happen to include as allowed to actually commit, you mean. As opposed to everyone that can sign themselves up for bugzilla? It is designed to be more open and more easily fixable. Sure. More open then a self-registering system. Gotcha. -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux signature.asc Description: This is a digitally signed message part
