public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Chad M. Huneycutt" <chad.huneycutt@acm.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Experiences with rc5: emerge clobbering its own config, depmod & emerge screaming, BitchX symlink error
Date: Fri Aug  3 07:01:02 2001	[thread overview]
Message-ID: <3B6A9F91.7030202@acm.org> (raw)
In-Reply-To: 87elqt71cy.fsf@codefactory.se

Mikael Hallendal wrote:

>Ben Lutgens <blutgens@sistina.com> writes:
>
>>On Thu, Aug 02, 2001 at 01:34:44PM -0400, Chad M. Huneycutt wrote:
>>
>>>Daniel Robbins wrote:
>>>
>>>Actually, I have fixed gzip and gdbm.  I will fix the others by the
>>>end of this week.  And I want to reiterate that all developers please
>>>look at my previous posts about info files and make sure they check
>>>any new ebuilds.  I have seen a couple packages showing info errors
>>>lately.
>>>
>>The authors name is at the top of the ebuild. Perhaps we should send a
>>polite email outlining the error.
>>
>
>Hi!
>
>I think this too, perhaps send an email to both the AUTHOR and the
>last commiter to that package. Another possibility is to add all
>ebuilds that do this wrong under an wiki-todo so that every developer
>can look there to see if someone else has found errors in one of your
>ebuilds. I'm not sure about mine, haven't looked into it yet, so feel
>free to flame me for broken ebuilds :)
>
I believe the reason drobbins added the nag message to the end of the 
ebuild process was so that ebuild maintainers would know that their 
ebuilds had the info problem.  Thus, I don't think any e-mails are 
necessary.
Developers: do an emerge --pretend, and check the list of broken infos. 
 If one of yours is listed, then fix it.  I will do a cvs update before 
I fix a package to make sure I don't duplicate work (or just to be safe, 
you can e-mail me if you are going to fix your own).

Chad

>






      reply	other threads:[~2001-08-03 13:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E15SG94-0004xg-00@cvs.gentoo.org>
2001-08-02  9:58 ` [gentoo-dev] Experiences with rc5: emerge clobbering its own config, depmod & emerge screaming, BitchX symlink error Iain Craig
2001-08-02 10:06   ` Daniel Robbins
2001-08-02 10:19     ` [gentoo-dev] new-mirror Djamil ESSAISSI
2001-08-03  7:17       ` Djamil ESSAISSI
2001-08-02 11:39     ` [gentoo-dev] Experiences with rc5: emerge clobbering its own config, depmod & emerge screaming, BitchX symlink error Chad M. Huneycutt
2001-08-02 11:43       ` Daniel Robbins
2001-08-02 12:56       ` Ben Lutgens
2001-08-03  6:54         ` Mikael Hallendal
2001-08-03  7:01           ` Chad M. Huneycutt [this message]

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=3B6A9F91.7030202@acm.org \
    --to=chad.huneycutt@acm.org \
    --cc=gentoo-dev@cvs.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