public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexander Gretencord <arutha@gmx.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [last rites] media-gfx/sodipodi
Date: Sun, 2 Apr 2006 19:48:43 -0400	[thread overview]
Message-ID: <200604021948.43378.arutha@gmx.de> (raw)
In-Reply-To: <200604022324.06077.carlo@gentoo.org>

On Sunday 02 April 2006 17:23, Carsten Lohrke wrote:
> This is not the case. At least unless the user actively looks at
> package.mask. Since Portage doesn't provide the information, this point is
> void. And even if - four weeks are a too long, imho.

As Andrej Kacian already noted, there are quite some people that don't sync 
every week. My general feeling is that most gentoo devs are far too fast in 
their decision/actions. As I already stated elsewhere in this thread, I 
generally only sync when I need to upgrade for feature/bug-/security-fixes 
and I don't see why that would be a bad idea. That way I get the benefits of 
gentoo but don't spend all day merging stuff that will have a new version two 
hours later :)

Regarding your argument that you have to be actively looking at p.mask, that 
is not entirely true because a verbose world/system merge will tell you about 
a masked package, although I do think that this is not enough and even the 
message in verbose mode is not really noticeable. But just because portage 
does not really alert the user anyway, does not mean that masking first is 
bad, does it? I think the reporting of missing/masked packages in portage has 
to be improved, instead of removing the masking process :)

Just my 0.02EUR.


Alex
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2006-04-02 23:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-29 10:06 [gentoo-dev] [last rites] media-gfx/sodipodi foser
2006-03-29 23:55 ` Mark Loeser
2006-03-30 17:05   ` [gentoo-dev] up for removal timeframe foser
2006-04-01 17:18   ` [gentoo-dev] [last rites] media-gfx/sodipodi Carsten Lohrke
2006-04-02  2:48     ` Daniel Goller
2006-04-02 19:20       ` Carsten Lohrke
2006-04-02 19:31         ` Ciaran McCreesh
2006-04-02 20:20           ` Carsten Lohrke
2006-04-02 20:29             ` Simon Stelling
2006-04-02 21:23               ` Carsten Lohrke
2006-04-02 21:42                 ` Marcelo Góes
2006-04-02 21:56                   ` Andrej Kacian
2006-04-02 23:48                 ` Alexander Gretencord [this message]
2006-04-03 11:21                 ` Simon Stelling
2006-04-03 11:27                   ` Simon Stelling
2006-04-03 14:41                 ` Jan Kundrát
2006-04-03 16:17                   ` Jan Kundrát
2006-04-02 20:33             ` Ciaran McCreesh
2006-04-02 21:18               ` Carsten Lohrke
2006-04-02 21:26                 ` Jakub Moc
2006-04-02 22:15                   ` Carsten Lohrke
2006-04-03  2:29         ` Daniel Goller
2006-04-02  3:52     ` Mark Loeser
2006-04-02 19:04       ` Alexander Gretencord
2006-04-02 19:12         ` Jan Kundrát
2006-04-02 23:36           ` Alexander Gretencord

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=200604021948.43378.arutha@gmx.de \
    --to=arutha@gmx.de \
    --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