On Fri, 2005-05-20 at 15:23 +0200, Paul de Vrieze wrote:
> in any case it should be _pY as your snapshot is newer than the current
> version. _p stands for patch level, _pre for prerelease. In case of cvs
> ebuilds patch levels are more appropriate as the new version is often not
> known.
Thank
On Tuesday 17 May 2005 10:27, Marius Mauch wrote:
>
> Well, it's valid with portage-2.1, but not 2.0.
Concerning that, how far are we from it being testable by the general
developer population?
Paul
--
Paul de Vrieze
Gentoo Developer
Mail: [EMAIL PROTECTED]
Homepage: http://www.devrieze.net
On Monday 16 May 2005 15:04, Henrik Brix Andersen wrote:
>
> The current ebuild is orinoco-0.15_rc2-r2.ebuild, and the logical name
> for a CVS snapshot would, as I see it, be
> orinoco-0.15_rc2_pre20050516.ebuild, but mixing _rcX and _preY is not
> allowed by portage.
in any case it should be _pY
Georgi Georgiev wrote:
maillog: 16/05/2005-11:46:15(-0700): Donnie Berkholz types
Henrik Brix Andersen wrote:
The current ebuild is orinoco-0.15_rc2-r2.ebuild, and the logical name
for a CVS snapshot would, as I see it, be
orinoco-0.15_rc2_pre20050516.ebuild, but mixing _rcX and _preY is not
allowe
maillog: 16/05/2005-11:46:15(-0700): Donnie Berkholz types
> Henrik Brix Andersen wrote:
> > The current ebuild is orinoco-0.15_rc2-r2.ebuild, and the logical name
> > for a CVS snapshot would, as I see it, be
> > orinoco-0.15_rc2_pre20050516.ebuild, but mixing _rcX and _preY is not
> > allowed by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Henrik Brix Andersen wrote:
> The current ebuild is orinoco-0.15_rc2-r2.ebuild, and the logical name
> for a CVS snapshot would, as I see it, be
> orinoco-0.15_rc2_pre20050516.ebuild, but mixing _rcX and _preY is not
> allowed by portage.
>
> I can't
On Mon, 2005-05-16 at 15:04 +0200, Henrik Brix Andersen wrote:
> The current ebuild is orinoco-0.15_rc2-r2.ebuild, and the logical name
> for a CVS snapshot would, as I see it, be
> orinoco-0.15_rc2_pre20050516.ebuild, but mixing _rcX and _preY is not
> allowed by portage.
I meant to write 'orinoc
Henrik Brix Andersen <[EMAIL PROTECTED]> wrote:
> I guess I could go with a simple -rX bump, but that wouldn't really
> reflect what the ebuild is - and I'd hate to have to add either a live
> CVS ebuild or a brand new net-wireless/orinoco-usb ebuild, since that
> would duplicate functionality, add
Hi all,
In attempting to solve bug #29937 [1] I would like to add a CVS snapshot
of the current net-wireless/orinoco driver - but I am faced with a
problem trying to come up with a proper naming scheme for this new
ebuild.
The current ebuild is orinoco-0.15_rc2-r2.ebuild, and the logical name
for
