On Wed, Jul 13, 2005 at 11:47:14AM -0400, Chris Gianelloni wrote:
> > I absolutely agree, but I am not associated with them in any way and
> > therefore am not in a possition to convince them to reconsider their
> > versioning policy (unfortunately).
> Why not just ask them? I've found that some p
On Wed, 2005-07-13 at 10:11 +0200, Anders Bruun Olsen wrote:
> > imho, projects who use those sort of versioning schemas should probably
> > rethink wtf the version # means to them
>
> I absolutely agree, but I am not associated with them in any way and
> therefore am not in a possition to convin
On Tue, Jul 12, 2005 at 08:51:42AM -0400, Mike Frysinger wrote:
> > I am working on an ebuild for open-iscsi (linux-iscsi-5.0.0.0.3rc6-363)
> > and would like to know what the best way of dealing with that totally
> > insane versionnumber is.
> > Right now I have the ebuild named linux-iscsi-5.0.0.
On Tuesday 12 July 2005 05:59 am, Anders Bruun Olsen wrote:
> I am working on an ebuild for open-iscsi (linux-iscsi-5.0.0.0.3rc6-363)
> and would like to know what the best way of dealing with that totally
> insane versionnumber is.
> Right now I have the ebuild named linux-iscsi-5.0.0.0.3_rc6363.e
Hi,
I am working on an ebuild for open-iscsi (linux-iscsi-5.0.0.0.3rc6-363)
and would like to know what the best way of dealing with that totally
insane versionnumber is.
Right now I have the ebuild named linux-iscsi-5.0.0.0.3_rc6363.ebuild
and then set $MY_PV and $MY_P manually.
Is there a better
