public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Thomas Sachau <tommy@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] overlay usage and maintainence [was: DistroWatch and Gentoo packages: status quo and future]
Date: Sun, 13 Sep 2009 13:30:13 +0200	[thread overview]
Message-ID: <4AACD7C5.2080703@gentoo.org> (raw)
In-Reply-To: <4AACCDBF.5020207@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2693 bytes --]

Richard Freeman schrieb:
> Jesús Guerrero wrote:
>>
>> Most Gentoo users will have no problem to use overlays as they need
>> them. If we had more developers we could as maintain more packages,
>> as simple as that.
>>
> 
> I actually tend to agree with this position, however to use overlays as
> a valid solution for end-users we need to do more to support them. Right
> now it is at least a little painful to get set up with an overlay.

I dont see any problem with "emerge layman; layman -L; layman -a <your preferred overlay>"

> Sure, overlays.g.o has tons of overlays - but which ones are
> mostly-stable, and which ones are intended to break systems?  What is
> the QA policy for each overlay?  If I'm an end-user not interested in
> breaking my system, what overlays are safe for me to use?

If developers create safe-to-use overlays, then i think, there is something wrong. Those ebuilds
shouldnt be hidden in any overlay, but instead be added and maintained in the main tree.

> If we really want overlays to be an outlet to allow more non-devs to
> contribute, then there needs to be some way to standardize them.  Maybe
> a simple ratings system - an overlay needs to comply with one set of
> rules just to get listed on o.g.o.  If you want to be marked as stable,
> then you obey some additional rules.  And so on...

If you want to use overlays to allow users to contribute and want to check the rules, you need devs,
who at least do basic QA checks on the overlay and all ebuilds. If this is done anyway, those devs
could also be proxy-maintainers. So those ebuilds, which comply to a set of rules could also go into
the main tree.

> 
> Then we can have overlays of various types for various purposes, and
> users can pick which ones they want to follow.  We could also have
> things like overlay groups - like "stable" or "desktop" or "KDE" / etc.
> 
> Maybe a fancy GUI to allow users to configure all of this.
> 
> Of course, for this to work somebody needs to develop it.  If somebody
> were willing to do the work I doubt anybody would get in their way.  It
> isn't like any of this would interfere with anybody who just wanted to
> make their own overlay without rules and not have it listed on some
> official site.

I think, this is the wrong direction. Instead of moving more and more things into overlays, we
should keep as much as possible in our main tree. With those two sets above removed, overlays would
either contain breaking stuff (playground for devs) or not checked ebuilds from users. For both
sets, the above ussage with layman should be easy enough.


-- 
Thomas Sachau

Gentoo Linux Developer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  parent reply	other threads:[~2009-09-13 11:30 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 23:02 [gentoo-dev] DistroWatch and Gentoo packages: status quo and future Sebastian Pipping
2009-09-12  2:24 ` [gentoo-dev] " Ryan Hill
2009-09-12 12:15   ` Sebastian Pipping
2009-09-14  2:46     ` Ryan Hill
2009-09-29  1:08       ` Donnie Berkholz
2009-09-12  4:48 ` [gentoo-dev] " Aaron Bauman
2009-09-12 17:26   ` Sebastian Pipping
2009-09-12 11:23 ` Marijn Schouten (hkBst)
2009-09-12 17:29   ` Sebastian Pipping
2009-09-13  9:11 ` Jesús Guerrero
2009-09-13 10:47   ` Richard Freeman
2009-09-13 10:57     ` Jesús Guerrero
2009-09-13 13:24       ` Richard Freeman
2009-09-13 19:39         ` Sebastian Pipping
2009-09-13 19:38       ` Sebastian Pipping
2009-09-13 11:30     ` Thomas Sachau [this message]
2009-09-13 18:57       ` [gentoo-dev] overlay usage and maintainence [was: DistroWatch and Gentoo packages: status quo and future] Patrick Lauer
2009-09-13 19:03         ` Jesús Guerrero
2009-09-13 19:41           ` Patrick Lauer
2009-09-13 20:04             ` Jesús Guerrero
2009-09-13 19:25         ` Alexander Færøy
2009-09-13 19:45           ` Sebastian Pipping
2009-09-13 20:00             ` Alexander Færøy
2009-09-13 20:02             ` Ciaran McCreesh
2009-09-13 20:17               ` Sebastian Pipping
2009-09-14 14:05                 ` Ciaran McCreesh
2009-09-14 18:28                   ` Sebastian Pipping
2009-09-14 18:51                     ` Ciaran McCreesh
2009-09-14 22:03                     ` Zac Medico
2009-09-16 20:31                       ` Sebastian Pipping
2009-09-16 21:21                         ` Zac Medico
2009-09-13 13:59   ` [gentoo-dev] Re: DistroWatch and Gentoo packages: status quo and future Duncan
2009-09-13 14:36     ` Dale
2009-09-13 15:05       ` Albert Hopkins
2009-09-13 15:45         ` Dale
2009-09-13 19:52           ` Sebastian Pipping
2009-09-13 21:25             ` Dale
2009-09-13 21:54               ` Alex Legler
2009-09-13 22:08                 ` Dale
2009-09-13 22:53                   ` Alex Legler
2009-09-13 23:06                     ` Dale
2009-09-13 20:00     ` Sebastian Pipping
2009-09-20 19:12       ` Duncan
2009-09-21  2:10         ` Angelo Arrifano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AACD7C5.2080703@gentoo.org \
    --to=tommy@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox