| 1 |
On Tue, Jul 12, 2005 at 08:51:42AM -0400, Mike Frysinger wrote: |
| 2 |
> > I am working on an ebuild for open-iscsi (linux-iscsi-5.0.0.0.3rc6-363) |
| 3 |
> > and would like to know what the best way of dealing with that totally |
| 4 |
> > insane versionnumber is. |
| 5 |
> > Right now I have the ebuild named linux-iscsi-5.0.0.0.3_rc6363.ebuild |
| 6 |
> > and then set $MY_PV and $MY_P manually. |
| 7 |
> > Is there a better way? |
| 8 |
> none that i'm aware of :/ |
| 9 |
|
| 10 |
Okay, it will have to do then. |
| 11 |
|
| 12 |
> imho, projects who use those sort of versioning schemas should probably |
| 13 |
> rethink wtf the version # means to them |
| 14 |
|
| 15 |
I absolutely agree, but I am not associated with them in any way and |
| 16 |
therefore am not in a possition to convince them to reconsider their |
| 17 |
versioning policy (unfortunately). |
| 18 |
|
| 19 |
-- |
| 20 |
Anders |
| 21 |
-----BEGIN GEEK CODE BLOCK----- |
| 22 |
Version: 3.12 |
| 23 |
GCS/O d--@ s:+ a-- C++ UL+++$ P++ L+++ E- W+ N(+) o K? w O-- M- V |
| 24 |
PS+ PE@ Y+ PGP+ t 5 X R+ tv+ b++ DI+++ D+ G e- h !r y? |
| 25 |
------END GEEK CODE BLOCK------ |
| 26 |
PGPKey: http://random.sks.keyserver.penguin.de:11371/pks/lookup?op=get&search=0xD4DEFED0 |
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives