[blfs-dev] GNOME Support Libs

Armin K. krejzi at email.com
Mon Aug 20 15:09:23 PDT 2012


On 08/20/2012 11:52 PM, Randy McMurchy wrote:
> Armin K. wrote these words on 08/20/12 16:21 CST:
>
>> Yes, I almost agree, but GNOME itself makes point releases, so it is
>> easier for person that upgrades from lets say 3.4.0 to 3.4.1 to upgrade
>> everything. The exception would be the fixes after official releases -
>> 3.4.1 was last official GNOME release, but some packages are at .4
>> already, so in that case you can create tickets if you like.
>
> Where it gets sticky is a package like libcroco. It is a dependency of two
> other packages in the book, gnome-shell and librsvg (required dependency in
> both packages). However, librsvg is used in all kinds of stuff. So, what if
> there is an update to libcroco? Do we not identify that and just let it go
> until a GNOME update?
>
> I think not. I think a ticket should be created, someone accept the ticket,
> look at the changelog, consult this list if need be, and then update the
> package. The BLFS GNOME maintainer could also update the package and see
> if it breaks his installed copy of GNOME.
>
> Does this procedure sound reasonable?
>

Well, as I said, as long there are GNOME point releases, the updated 
stable tarballs are mostly released in their 3 day tarballs-due period. 
If something is released earlier, then you are right, ticked should be 
created and if necesary fixed asap. Same for packages that come out 
after scheduled GNOME point releases. I mostly keep look at GNOME 
servers every few days to see if there are new packages.

I noticed there are Evolution and Evolution Data Server 3.4.4 updates, 
but I won't upgrade them because I want to focus on 3.6 release yet. If 
you like, you can create ticket for them and someone will maybe accept it.

Also, there are cases when you must upgrade some non-GNOME package (read 
as not part of GNOME core nor GNOME apps) to upgrade GNOME package. I 
experienced that part with WebKitGTK+ and Epiphany, where I had to 
upgrade WebKitGTK+ (which is not officialy part of GNOME but it is used 
for many GNOME components) to latest version in order to upgrade Epiphany.

And as you already said, GTK+ project covers more than just GNOME, but 
it's major upgrades can hurt GNOME if it's upgraded to latest stable 
before GNOME itself is upgraded. That's why I was talking about one 
ticket for all of those packages (at least for first set of new stable 
releases). Point releases are easy to manage tough as for them only 
md5sum and maybe tarball and build size changes in most cases.



More information about the blfs-dev mailing list