public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Alexander Færøy" <ahf@0x90.dk>
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 21:25:13 +0200	[thread overview]
Message-ID: <20090913192513.GA26237@anubis.0x90.dk> (raw)
In-Reply-To: <200909132057.48975.patrick@gentoo.org>

On Sun, Sep 13, 2009 at 08:57:48PM +0200, Patrick Lauer wrote:
> First issue: How do I find out in which overlay stuff is?

Paludis' solution to that issue is the unavailable repository[1].  It is
a repository that contains enough information about the packages in the
repositories to display information about them without being able to
install them. It works surprisingly well and it might be an idea worth
looking at.

> Second issue: "I want foopackage and barpackage, but not your hacked gcc"
> Overlays can overshadow tree packages, which can have undesired effects.

Support for overlay information in package.mask?


[1] http://paludis.pioto.org/configuration/repositories/unavailable.html

-- 
Alexander Færøy



  parent reply	other threads:[~2009-09-13 19: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     ` [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
2009-09-13 19:25         ` Alexander Færøy [this message]
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=20090913192513.GA26237@anubis.0x90.dk \
    --to=ahf@0x90.dk \
    --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