From: Patrick Kursawe <phosphan@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] How to fix pathnames in .ebuilds
Date: Fri, 11 Jul 2003 07:40:58 +0200 [thread overview]
Message-ID: <20030711054058.GA8055@zaphod.anachem.ruhr-uni-bochum.de> (raw)
In-Reply-To: <874r1ujqcb.fsf@kirk.better-com.de>
[-- Attachment #1: Type: text/plain, Size: 939 bytes --]
On Thu, Jul 10, 2003 at 06:31:32PM +0200, Martin Lesser wrote:
> Before reporting this ebuild to bugs.gentoo.org I would like to know how
> long the "normal" period is between reporting a new ebuild and finding
> this ebuild in the portage tree (or getting any other response)- another
> ebuild was added on 05/31/03
> (http://bugs.gentoo.org/show_bug.cgi?id=22000) but since then not much
> happened...
I'm afraid there is nothing like a "normal" period. It depends on quite
a few factors... for example, if a developer is interested in the program,
if he thinks he will be able to maintain it, how clean the ebuild looks,
air pressure, moon phase...
> IMO creating or reporting ebuilds which perhaps are only helpful here
> doesn't make much sense.
Perhaps someone else who needs it will find it when searching
bugs.gentoo.org for it. Try to see it as a "user contributed ebuilds"
database aswell.
Bye, Patrick
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-07-11 5:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-10 12:16 [gentoo-dev] How to fix pathnames in .ebuilds Martin Lesser
2003-07-10 12:40 ` Alastair Tse
2003-07-10 16:31 ` Martin Lesser
2003-07-11 5:40 ` Patrick Kursawe [this message]
2003-07-11 9:16 ` Paul de Vrieze
2003-07-12 22:40 ` Stanislav Brabec
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=20030711054058.GA8055@zaphod.anachem.ruhr-uni-bochum.de \
--to=phosphan@gentoo.org \
--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