From: Lance Albertson <ramereth@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: sys-pam category
Date: Sun, 05 Jun 2005 13:10:24 -0500 [thread overview]
Message-ID: <1117995024.22710.75.camel@pursuit> (raw)
In-Reply-To: <200506051350.15778.mcummings@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1217 bytes --]
On Sun, 2005-06-05 at 13:50 -0400, Michael Cummings wrote:
> Solar,
> I realize you meant this as a general statement of opinion and not a
> flame-baiter, but can you elaborate on:
>
> On Sunday 05 June 2005 11:37, Ned Ludd wrote:
> > Invalidates binary package trees.
>
> My (wrong?) understanding was that this is addressed when portage runs a
> fixpackages (otherwise what's it doing to all those binary packages?). I ask
> because its no secret that I'm working on a split up of dev-perl from the
> 500+ packages to a better organized, reasonable scenario where packages are
> categorized based on, well, category :) rather than on the fact that they
> "contain some perl bits or module bits, stuff them in dev-perl".
In my experience, fixpackages doesn't actually fix this sometimes. I've
had to phsyically delete the binary package and recreate it for the
category to be fixed. Sadly, I haven't had time to search for a bug on
it.
--
Lance Albertson <ramereth@gentoo.org>
Gentoo Infrastructure | Operations Manager
---
GPG Public Key: <http://www.ramereth.net/lance.asc>
Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742
ramereth/irc.freenode.net
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-06-05 18:10 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-05 14:22 [gentoo-dev] Proposal: sys-pam category Diego 'Flameeyes' Pettenò
2005-06-05 14:44 ` Alin Nastac
2005-06-06 0:34 ` Mike Doty
2005-06-06 4:00 ` Alin Nastac
2005-06-05 15:37 ` Ned Ludd
2005-06-05 16:34 ` Jonas Geiregat
2005-06-05 16:42 ` foser
2005-06-05 17:25 ` Nathan L. Adams
2005-06-05 18:13 ` Ned Ludd
2005-06-05 20:57 ` Nathan L. Adams
2005-06-05 21:03 ` Nathan L. Adams
2005-06-05 21:55 ` Ned Ludd
2005-06-06 10:43 ` Jan Jitse Venselaar
2005-06-05 19:13 ` Jonas Geiregat
2005-06-05 17:34 ` Diego 'Flameeyes' Pettenò
2005-06-05 19:03 ` Ned Ludd
2005-06-05 19:21 ` Diego 'Flameeyes' Pettenò
2005-06-05 20:13 ` Ned Ludd
2005-06-06 19:47 ` Kevin F. Quinn
2005-06-05 17:50 ` Michael Cummings
2005-06-05 18:10 ` Lance Albertson [this message]
2005-06-06 14:06 ` [gentoo-dev] " sf
2005-06-06 14:29 ` Jason Stubbs
2005-06-05 15:59 ` [gentoo-dev] " Ian Leitch
2005-06-05 22:03 ` Robin H. Johnson
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=1117995024.22710.75.camel@pursuit \
--to=ramereth@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