public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jesús Guerrero" <i92guboj@terra.es>
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 22:04:20 +0200	[thread overview]
Message-ID: <92d1a560df57aa01b0ef304545c51ab3@localhost> (raw)
In-Reply-To: <200909132141.13870.patrick@gentoo.org>

On Sun, 13 Sep 2009 21:41:13 +0200, Patrick Lauer <patrick@gentoo.org>
wrote:
> On Sunday 13 September 2009 21:03:13 Jesús Guerrero wrote:
>> On Sun, 13 Sep 2009 20:57:48 +0200, Patrick Lauer <patrick@gentoo.org>
>> 
>> wrote:
>> > First issue: How do I find out in which overlay stuff is?
>> 
>> http://gentoo.zapto.org/
> 
> That's not an official project, not mentioned in the layman docs afaik
> (feel 
> free to prove me wrong :) ) and only list the overlays in the layman
> config.
> It's just one step above "fetch from the bugzilla bug" ;)
> (Ok, I'm exaggerating a bit, but it's still very user-unfriendly ...)

I don't know what your point there is. Layman is not official either as
far as I know, and the overlays are unsupported by Gentoo directly.

>> > Second issue: "I want foopackage and barpackage, but not your hacked
>> > gcc"
>> > Overlays can overshadow tree packages, which can have undesired
>> > effects.
>> 
>> Smart overlays shouldn't do that (and if you are using ~arch then it's
>> *your* problem). 
> How would you avoid it? If I had an overlay I'd dump everything in it
that 
> looks remotely interesting to me, and I don't care what you think should
> be in 
> my overlay ;)

How? ~arch keywords? And, if you are in ~arch, then you are smart enough
to live with this as well.

>> Yep. All comes down to the same, lack of man power I think.
> Always. And if you ever think you're done some users file some new bugs
:)
> So if you feel unhappy about things go fix them. You have the power!
> (And any excuse that you are not talented enough or whatever ... look,
> they 
> let me commit to the tree too!)
> 
> Plus there's all the other fronts in the battle for the best linux
distro. 
> Bugwrangling, documentation maintenance, security issues, ... there are
> enough 
> possibilities even for those that can't or don't want to work on ebuilds

> directly. Just start working on stuff, ask when you need help and it'll
be 
> even better soon.
> 
> See? It's easy. And you have no excuse not to help. Now just do stuff!
:)

No. It's not me who's unhappy about the current status of things ;)

I already do my work in other areas and I have no more time than I
devote to Gentoo already. I maintain overlays to a minimum, and when
I need an overlay I just pick it and put it into my personal overlay.

Yes, every forum staffer could very well become a developer and spend
their time doing some ebuilding, but then we would have a crappy forum
full of spam (believe me, it takes time to keep it clean) :)
-- 
Jesús Guerrero



  reply	other threads:[~2009-09-13 20:04 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     ` [gentoo-dev] overlay usage and maintainence [was: DistroWatch and Gentoo packages: status quo and future] Thomas Sachau
2009-09-13 18:57       ` 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 [this message]
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=92d1a560df57aa01b0ef304545c51ab3@localhost \
    --to=i92guboj@terra.es \
    --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