public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: AGottinger@t-online.de (Achim Gottinger)
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] new package
Date: Thu Feb 22 10:42:01 2001	[thread overview]
Message-ID: <3A954941.7C00C7C7@gottinger.de> (raw)
In-Reply-To: 20010222123641.B853@kabbu.reston.redhat.com

"Jerry A!" wrote:
> 
> On Thu, Feb 22, 2001 at 05:45:45PM +0100, Achim Gottinger wrote:
> : "Jerry A!" wrote:
> : >
> : > I'll do it.  I'll just have to be very careful.  I'll probably start
> : > tackling it by the beginning of next week.  And I'll make sure I give a
> : > general alert/heads up.
> :
> : The only package that really needs care is ORBit. About 50 packages are
> : in dev-perl.
> : I personaly thought that using the sources name as we did it till now
> : makes more sense since it reduces the typing in the scripts.
> : But if you guys are not happy with that change it.
> 
> Hmm...  Something to consider here.  I was thinking that user
> expectations are for things to be consistent.  You know, we could always
> try and modify the portage code to ignore case.
> 
> Daniel, what do you think of that?
> 
> : PS: Jerry have you tested pgcc and is there a package in the tree that I
> : can use here?
> 
> Sorry, it's still sitting on my machine waiting for some more tests.
> I'm one of those people who hates committing anything to a tree before
> unless it's more-or-less done.  I'll commit what I have when I get home.
> 

Well that doesn't work for me because I'm testing packages during
development on different machines with different ARCH,OPT and USE flags.
But I only change current-packages if I'm sure the package is stable.

achim~

>         --Jerry
> 
> name:  Jerry Alexandratos         ||  Open-Source software isn't a
> phone: 703.599.6023               ||  matter of life or death...
> email: jerry@thehutt.org          ||  ...It's much more important
>                                   ||  than that!
> 
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://www.gentoo.org/mailman/listinfo/gentoo-dev



  reply	other threads:[~2001-02-22 17:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-20 16:19 [gentoo-dev] new package Pete Gavin
2001-02-20 16:23 ` Jerry A!
2001-02-20 16:35   ` Pete Gavin
2001-02-20 17:43   ` drobbins
2001-02-22  9:22   ` Pete Gavin
2001-02-22  9:29   ` Achim Gottinger
2001-02-22  9:37   ` Achim Gottinger
2001-02-22  9:58     ` Jerry A!
2001-02-22 10:12       ` Achim Gottinger
2001-02-22 10:29         ` drobbins
2001-02-22 10:36           ` Achim Gottinger
2001-02-22 11:05             ` Jerry A!
2001-02-22 11:07               ` drobbins
2001-02-22 11:37                 ` Jerry A!
2001-02-22 12:10                   ` Achim Gottinger
2001-02-22 12:12                     ` drobbins
2001-02-22 12:27                       ` Achim Gottinger
2001-02-22 12:48                         ` Jerry A!
2001-02-22 11:24               ` Achim Gottinger
2001-02-22 10:37         ` Jerry A!
2001-02-22 10:42           ` Achim Gottinger [this message]
2001-02-22 11:02             ` Jerry A!
2001-02-22 11:46               ` Achim Gottinger
  -- strict thread matches above, loose matches on Subject: below --
2001-03-11 14:54 Pete Gavin
2001-03-11 15:51 ` drobbins

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=3A954941.7C00C7C7@gottinger.de \
    --to=agottinger@t-online.de \
    --cc=gentoo-dev@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