After today's release of portage-2.2.21, I merged the repoman re-write
code in to portage master branch. So, the code is functionally
identical to portage-2.2.21 with the exception of repoman. It is now
ready for more testing before it too is released in a normal portage
release. Please keep in
On 16.09.2015 09:15, Stefan G. Weichinger wrote:
> Well, my ebuilds for www-apps/otrs are in here already:
>
> https://github.com/stefangweichinger/gentoo-overlay/tree/master/www-apps/otrs
>
> (the other packages in that overlay aren't that up to date ... simply
> some work collected over the ye
On 21/09/2015 21:45, Taahir Ahmed wrote:
>
> Instead of adding more and more layers to the Gentoo versioning spec to
> work around insane upstreams, why not put the relative ordering of
> versions into the ebuilds?
>
> Then, a version identifier would just be a unique string.
>
> An ebuild would
On Mon, 21 Sep 2015 14:45:19 -0500
Taahir Ahmed wrote:
> Instead of adding more and more layers to the Gentoo versioning spec
> to work around insane upstreams, why not put the relative ordering of
> versions into the ebuilds?
That idea was what lead to Zynot...
--
Ciaran McCreesh
signature.a
Instead of adding more and more layers to the Gentoo versioning spec to
work around insane upstreams, why not put the relative ordering of
versions into the ebuilds?
Then, a version identifier would just be a unique string.
An ebuild would declare which version strings it succeeds.
Then even in
# Michael Orlitzky (21 Sep 2015)
# Mask for removal in 30 days. Obsolete. Bug #561040.
dev-php/smarty-docs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 20/09/15 11:26, Jeroen Roovers wrote:
> My personal policy is to completely ignore anything Gentoo related
> that gets posted on Github.
+1.
- --
Alexander
berna...@gentoo.org
https://secure.plaimi.net/~alexander
-BEGIN PGP SIGNATURE-
V
Hi!
On Sun, 20 Sep 2015, Anthony G. Basile wrote:
> On 9/20/15 1:23 PM, Ryan Hill wrote:
> >
> >> [0] I am pretty sure some arches will want to opt out of this
> >> scheme, at least for some more critical packages.
> > ALLARCHES shouldn't be used on critical packages.
>
> Exactly. So suppose th