Xfce 4.4.1 on Monday 09-apr [WAS Re: Xfce 4.4.1 ?]

Brian J. Tarricone bjt23 at cornell.edu
Sat Apr 7 09:03:52 CEST 2007


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sat, 07 Apr 2007 08:11:07 +0300 Jani Monoses wrote:

> > Then what's the problem?  We're not changing the lib numbering.  The
> > major/minor *library* version will remain the same; just the package
> > version will change.  As long as the libutil 4.4.1 Xubuntu package
> > hits your repository by the time xfdesktop 4.4.1 does, there's no
> > problem.
> 
> that is the problem in fact, that it needs to hit the repo before,
> causing a lag.
> 
> I'd rather not upload a practically no-change libutil (as the two
> bugfixes are already in from svn) just to allow xfdesktop to build.
> It is extra work both for me and for the archive managers. The
> archive is frozen so non-critical issues are just noise as everything
> needs explicit approval.

That's a shame, but Xubuntu isn't the only distro shipping Xfce, and
others may not have those patches in.  Some distros (like Gentoo, for
example), have package managers that don't pull in all updates when you
do a 'world update'; only packages that have explicitly been installed
by the user (and not deps that have been implicitly pulled in) get
updated with a normal update.  In this case, unless the xfdesktop
package has an explicit dep on libxfce4util 4.4.1, libutil won't get
updated.

On a side note, changes to xfdesktop since 4.4.0 have been minimal: if
you're happy with how it's performing now, just ship Xubuntu's next
release with your current libxfce4util-4.4.0+patches with whatever
xfdesktop you have in there.  Or, ship xfdesktop 4.4.0 plus a patch or
two - changes in r25032 and *maybe* r25031 are the only ones remotely
important.  I haven't had much time to fix bugs since 4.4.0; waiting
until 4.4.2 to update xfdesktop might make the least work for you
without much if any pain for your users.

> And while the current libutil bug is serious, where should the line
> be drawn in the future wrt bumping lib requirements not for API/ABI
> changes but for bugfixes?

In all seriousness, it's drawn wherever I want it to be drawn, and I
can feel free to erase it and redraw it when I think it's necessary.

	-brian

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (GNU/Linux)

iD8DBQFGF0Jg6XyW6VEeAnsRApPgAKCuhpGtkoHE2i2rgRAGQRIKUbLo9gCguhYz
aUac5JlG9e4ZQ+3y2VUtZKQ=
=9SY5
-----END PGP SIGNATURE-----


More information about the Xfce4-dev mailing list