Source Mage code commit list

[Florian Franzmann <siflfran AT hawo.net>]

On Mi 2014-03-26 17:15:08 +0100, Treeve Jelbert wrote:
> there are multiple development branches, some of which have not been 
> changed 
> for ages, others of which are updated more or less frequently.
> 
> 
> I am now seeing error reports or compile logs about programs in the master 
> branch which need newer versions of something which already exists in a 
> development  branch.
> 
> New versions of qt or kde now need libxkbcommon, which is only in 
> devel-xorg-
> modular.
> 
> $ gaze version libxkbcommon gcc icu libpng
> Grimoire    Section        Spell         Grimoire Version  Installed Version
> --------    -------        -----         ----------------  -----------------
> localrepos  misc           libxkbcommon  xkbcommon-0.4.0   xkbcommon-0.4.0
> smgl        gnu            gcc           4.6.4             4.8.2
> smgl        libs           icu           4.8.1.1           52.1
> smgl        graphics-libs  libpng        1.2.51            1.6.10
> 
> Note that gcc-4.9 and icu-53 are expected in early April.
> 
> 
> 
> I would like to propose that devel-gcc-4.8, devel-icu and devel-libpng-1.6 
> be 
> merged immediately into devel-xorg-modular, which can stabliise for a short 
> period and then merge  devel-xorg-modular to master.
I'm all in favour of that. The problem with these branches is not that
there are any spells that don't build with the development branches.
The problem is that we don't have a migration path from our current
master to the development branches. For example, migrating to the new
version of icu will break lots and lots of installed spells since,
unlike gentoo, we do not preserve old libraries until they aren't
needed anymore. In principle, cleanse --fix should be able to take
care of the situation, however, it fails to do so.

Honestly, I don't think that we will come up with a working migration
path. We've had this situation for over a year now and nobody has
has been able to solve it.

The reason that we don't have gcc in test yet is that it produces
incorrect code for the version of xorg we have in test. So as soon as
we have merged xorg into test, gcc shouldn't be a problem at all.

I haven't tried the libpng branch so far but I think it has similar
problems as the icu branch.

regards
Florian
> 
> 
> This would have the advantage of reducing the number of rebuilds because of 
> some of these  updates.
> 
> There may be other development branches which I do not track.
> 
> If there are any spells which will only build with an old version of gcc, 
> icu 
> or libpng they should explicitly depend on gcc-4.6, icu-4.8 or libpng-1.2 
> spells.
> 
> 
> Regards, Treeve
> _______________________________________________
> SM-Commit mailing list
> SM-Commit AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/sm-commit
> 

--