| 1 |
Hi all, |
| 2 |
|
| 3 |
I've just wanted to package xdvik-22.40y1 (patch release of |
| 4 |
xdvik-22.40y). First I named it as xdvik-22.40y_p1.ebuild: |
| 5 |
|
| 6 |
rico% ebuild xdvik-22.40y_p1.ebuild digest |
| 7 |
!!! Name error in 22.40y_p1: characters before _ must be numeric |
| 8 |
!!! Error: PF is null; exiting. |
| 9 |
|
| 10 |
Second, I tried xdvik-22.40y1.ebuild: |
| 11 |
|
| 12 |
rico% ebuild xdvik-22.40y1.ebuild digest |
| 13 |
!!! Name error in 22.40y1 |
| 14 |
!!! Error: PF is null; exiting. |
| 15 |
|
| 16 |
Third, xdvik-22.40y.1.ebuild: |
| 17 |
|
| 18 |
rico% ebuild xdvik-22.40y.1.ebuild digest |
| 19 |
!!! Name error in 22.40y.1: "40y" is not a valid version component. |
| 20 |
!!! Error: PF is null; exiting. |
| 21 |
|
| 22 |
After all, I couldn't make xdvik-22.40y1 ebuild :-( |
| 23 |
|
| 24 |
As far as I understand naming policy from Gentoo Linux documentation I |
| 25 |
think xdvik-22.40y_p1.ebuild is valid name (pkg = xdvik, ver = 22.40y, |
| 26 |
suf = p1) while the others are invalid, but Portage complains about |
| 27 |
all of them. Do I misunderstand naming policy or does it belong to |
| 28 |
Portage bug? How can I make an ebuild of xdvik-22.40y1? (I can name |
| 29 |
it xdvik-22.40y-r2.ebuild as the last resort :-/ ) |
| 30 |
|
| 31 |
|
| 32 |
regards, |
| 33 |
|
| 34 |
-- |
| 35 |
Mamoru KOMACHI <usata@g.o> |
| 36 |
http://dev.gentoo.org/~usata/ |
| 37 |
|
| 38 |
-- |
| 39 |
gentoo-dev@g.o mailing list |
Archives