From: Mamoru KOMACHI <usata@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] How to name xdvik-22.40y1 ebuild?
Date: Wed, 03 Sep 2003 15:56:12 +0900 [thread overview]
Message-ID: <86n0dml5rn.wl@rico.usata.org> (raw)
In-Reply-To: <20030903061516.GD10730@zaphod.anachem.ruhr-uni-bochum.de>
At Wed, 3 Sep 2003 08:15:16 +0200,
Patrick Kursawe wrote:
> > Do I misunderstand naming policy or does it belong to
> > Portage bug?
>
> File a bug and wait if it's marked as invalid :-)
All right, I filed a bug report -> http://bugs.gentoo.org/show_bug.cgi?id=27840
> > How can I make an ebuild of xdvik-22.40y1? (I can name
> > it xdvik-22.40y-r2.ebuild as the last resort :-/ )
>
> Please don't do that. The -r? part just means versioning of the ebuild,
> not of the package itself.
Sure, I didn't intend to do that ;-)
Thanks,
--
Mamoru KOMACHI <usata@gentoo.org>
http://dev.gentoo.org/~usata/
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-09-03 6:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 23:04 [gentoo-dev] How to name xdvik-22.40y1 ebuild? Mamoru KOMACHI
2003-09-03 6:15 ` Patrick Kursawe
2003-09-03 6:56 ` Mamoru KOMACHI [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=86n0dml5rn.wl@rico.usata.org \
--to=usata@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