-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Tue, 24 Jun 2014 21:25:40 +0200
Jörg Schaible wrote:
> Alexandre Rostovtsev wrote:
>
> > On Mon, 2014-06-23 at 22:15 +0200, Jörg Schaible wrote:
> >> So, why the heck, was the dependency to dev-libs/glib changed for
> >> an existing ebuild with
Jörg Schaible:
> Alexandre Rostovtsev wrote:
>
>> On Mon, 2014-06-23 at 22:15 +0200, Jörg Schaible wrote:
>>> So, why the heck, was the dependency to dev-libs/glib changed for an
>>> existing ebuild without increasing its version (e.g.
>>> dbus-glib-0.100.2-r2)?
>>
>> Please see http://article.gma
Kristian Fiskerstrand:
> On 06/24/2014 09:25 PM, Jörg Schaible wrote:
>> Alexandre Rostovtsev wrote:
>
>>> On Mon, 2014-06-23 at 22:15 +0200, Jörg Schaible wrote:
So, why the heck, was the dependency to dev-libs/glib changed
for an existing ebuild without increasing its version (e.g.
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 06/24/2014 09:25 PM, Jörg Schaible wrote:
> Alexandre Rostovtsev wrote:
>
>> On Mon, 2014-06-23 at 22:15 +0200, Jörg Schaible wrote:
>>> So, why the heck, was the dependency to dev-libs/glib changed
>>> for an existing ebuild without increasing i
Alexandre Rostovtsev wrote:
> On Mon, 2014-06-23 at 22:15 +0200, Jörg Schaible wrote:
>> So, why the heck, was the dependency to dev-libs/glib changed for an
>> existing ebuild without increasing its version (e.g.
>> dbus-glib-0.100.2-r2)?
>
> Please see http://article.gmane.org/gmane.linux.gento
Jörg Schaible posted on Mon, 23 Jun 2014 22:15:39 +0200 as excerpted:
> can somebody tell my, since when existing (and installed) ebuilds
> suddenly change without at least increasing the version number?
That has always been the case. Existing ebuilds aren't always bumped for
changes, only if
