public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Unused ebuild built_with_use cleanup
Date: Wed, 28 Oct 2009 12:11:07 +0100	[thread overview]
Message-ID: <20091028121107.380e5650@gentoo.org> (raw)
In-Reply-To: <4AE81426.6090106@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]

On Wed, 28 Oct 2009 11:51:34 +0200
Petteri Räty <betelgeuse@gentoo.org> wrote:

> Mike Frysinger wrote:
> > On Tuesday 27 October 2009 14:46:31 Petteri Räty wrote:
> >> Normally old versions are not kept around as already said if you
> >> read the thread.
> > 
> > "normal" is not the same thing as "always".  unless you're the
> > maintainer, you have no idea whether old versions are kept there on
> > purpose.  ive had people delete older versions of packages on me
> > simply because they made this invalid assumption without talking to
> > the maintainer.  the rest of the thread is irrelevant as this point
> > was not made.
> > 
> 
> Yes I have no idea. That's why I asked on gentoo-dev-announce for
> maintainers to tell me if they are kept on purpose so the point was
> made already at the very start.


Still, it has already been stated but: please file bugs! A big tracker
would probably be messy, one bug / herd or category could be better.
You did file some bugs at some point, where I was in the assigned herd
and did proceed quickly I think. Why did you stop? Some were just
straight removal, some did need some other removal in order to be clean
(this may be due to the fact that packages didnt work with latest
versions but didn't have restricted deps on the package that would have
to be removed).

I am not following -dev very carefully and am too lazy to dig in a list
posted on -dev-announce to find out if I need to do something or not. A
bug makes that easy to track and is the usual way of getting ebuild
changes done in the tree. We rant on users who report bugs on -dev, I'm
afraid the the same applies to developers :)


Also, remark that your script is flawed, I see some freebsd stuff in
your list which are certainly the best visible version on some
profiles. Again, this will be better tracked in a bug.


Alexis.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-10-28 11:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 13:32 [gentoo-dev] Unused ebuild built_with_use cleanup Petteri Räty
2009-10-07 11:21 ` Marijn Schouten (hkBst)
2009-10-08 21:29   ` Petteri Räty
2009-10-07 11:54 ` Stelian Ionescu
2009-10-08 21:34   ` Petteri Räty
2009-10-08 22:03     ` Jeremy Olexa
2009-10-08 22:22       ` Petteri Räty
2009-10-09  0:17         ` Patrick Lauer
2009-10-09 13:38           ` Petteri Räty
2009-10-08 22:25     ` Tomáš Chvátal
2009-10-09 13:41       ` Petteri Räty
2009-10-24 12:32 ` [gentoo-dev] Re: [gentoo-dev-announce] " Petteri Räty
2009-10-24 20:29   ` James Cloos
2009-10-25  9:48     ` Petteri Räty
2009-10-26 23:21       ` James Cloos
2009-10-27 13:12         ` Petteri Räty
2009-10-27  6:07       ` Ryan Hill
2009-10-27  7:02         ` Mike Frysinger
2009-10-27 13:09           ` Petteri Räty
2009-10-27 13:46             ` Mike Frysinger
2009-10-27 18:46               ` Petteri Räty
2009-10-28  2:31                 ` [gentoo-dev] " Mike Frysinger
2009-10-28  9:51                   ` Petteri Räty
2009-10-28 11:11                     ` Alexis Ballier [this message]
2009-10-30  2:29                     ` Doug Goldstein

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=20091028121107.380e5650@gentoo.org \
    --to=aballier@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