public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev]  New category: net-voip
Date: Tue, 18 Jul 2006 14:17:30 -0400	[thread overview]
Message-ID: <1153246650.31239.25.camel@onyx> (raw)
In-Reply-To: <20060718151541.5decd065@snowdrop.home>

On Tue, 2006-07-18 at 15:15 +0100, Ciaran McCreesh wrote:
> On Tue, 18 Jul 2006 09:34:37 -0400 Ned Ludd <solar@gentoo.org> wrote:
> | Creation of a new categories is fine. pkg moves are bad. 
> | See the countless other posting on this subject of why pkg 
> | moves are bad. 
> 
> Uh, as far as I recall, you've yet to come up with any technical
> explanation other than "it breaks one of my pet projects"... The gains
> of consistency and manageability far outweigh the minor inconvenience.

There is no consistency for end users when stuff keeps getting shuffled 
around. Portage still can't get it right. 'fixpackages' does not 
correct the installed vdb content so the problems extend past any of 
my pet projects.

-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-07-18 18:21 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18 12:53 [gentoo-dev] New category: net-voip Stefan Schweizer
2006-07-18 13:34 ` Ned Ludd
2006-07-18 13:51   ` [gentoo-dev] " Stefan Schweizer
2006-07-18 18:18     ` Ned Ludd
2006-07-18 14:15   ` [gentoo-dev] " Ciaran McCreesh
2006-07-18 18:17     ` Ned Ludd [this message]
2006-07-18 20:43       ` Ciaran McCreesh
     [not found]       ` <200607181739.49727.vapier@gentoo.org>
     [not found]         ` <1153321851.6243.20.camel@onyx>
2006-07-19 16:10           ` Ciaran McCreesh
2006-07-22 11:29             ` Ned Ludd
2006-07-22 11:42               ` Jakub Moc
2006-07-22 11:57                 ` Simon Stelling
2006-07-23 11:16                 ` Stuart Herbert
2006-07-19 18:22           ` [gentoo-dev] " Duncan
     [not found]     ` <20060718211822.379c65e1@c1358217.kevquinn.com>
2006-07-18 20:40       ` [gentoo-dev] " Ciaran McCreesh
2006-07-19  6:57         ` Kevin F. Quinn
2006-07-19 16:15           ` Ciaran McCreesh
2006-07-20  7:05             ` Kevin F. Quinn
2006-07-20  7:37               ` Brian Harring
2006-07-20 18:41                 ` Kevin F. Quinn
2006-07-20 20:24                   ` Brian Harring
2006-07-20 23:17                     ` Chris Gianelloni
2006-07-20 23:26                     ` Diego 'Flameeyes' Pettenò
2006-07-22  9:45                     ` Kevin F. Quinn
2006-07-20 16:27               ` Ciaran McCreesh
2006-07-21  7:44           ` Stuart Herbert
2006-07-21  8:05             ` Brian Harring
2006-07-21 14:49               ` Ciaran McCreesh
2006-07-22 16:04               ` Kevin F. Quinn
2006-07-22 20:35                 ` Brian Harring
2006-07-24 12:43                   ` Kevin F. Quinn
2006-07-22 20:42                 ` Ciaran McCreesh
2006-07-24 12:42                   ` Kevin F. Quinn
2006-07-23 11:19                 ` Stuart Herbert
2006-07-24 12:47                   ` Kevin F. Quinn
2006-07-24 13:23                     ` Brian Harring
2006-07-24 15:50                       ` Kevin F. Quinn
2006-07-24 16:30                         ` Ciaran McCreesh
2006-07-24 12:53                   ` Jakub Moc

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=1153246650.31239.25.camel@onyx \
    --to=solar@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