From: Mamoru KOMACHI <usata@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] How to name xdvik-22.40y1 ebuild?
Date: Wed, 03 Sep 2003 08:04:35 +0900 [thread overview]
Message-ID: <86wucqlrlo.wl@rico.usata.org> (raw)
Hi all,
I've just wanted to package xdvik-22.40y1 (patch release of
xdvik-22.40y). First I named it as xdvik-22.40y_p1.ebuild:
rico% ebuild xdvik-22.40y_p1.ebuild digest
!!! Name error in 22.40y_p1: characters before _ must be numeric
!!! Error: PF is null; exiting.
Second, I tried xdvik-22.40y1.ebuild:
rico% ebuild xdvik-22.40y1.ebuild digest
!!! Name error in 22.40y1
!!! Error: PF is null; exiting.
Third, xdvik-22.40y.1.ebuild:
rico% ebuild xdvik-22.40y.1.ebuild digest
!!! Name error in 22.40y.1: "40y" is not a valid version component.
!!! Error: PF is null; exiting.
After all, I couldn't make xdvik-22.40y1 ebuild :-(
As far as I understand naming policy from Gentoo Linux documentation I
think xdvik-22.40y_p1.ebuild is valid name (pkg = xdvik, ver = 22.40y,
suf = p1) while the others are invalid, but Portage complains about
all of them. Do I misunderstand naming policy or does it belong to
Portage bug? How can I make an ebuild of xdvik-22.40y1? (I can name
it xdvik-22.40y-r2.ebuild as the last resort :-/ )
regards,
--
Mamoru KOMACHI <usata@gentoo.org>
http://dev.gentoo.org/~usata/
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-09-02 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-02 23:04 Mamoru KOMACHI [this message]
2003-09-03 6:15 ` [gentoo-dev] How to name xdvik-22.40y1 ebuild? Patrick Kursawe
2003-09-03 6:56 ` Mamoru KOMACHI
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=86wucqlrlo.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