[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: [decision] new patch management system in xorg-x11



On Sun, Jun 05, 2005 at 11:03:39PM -0400, David Nusinow wrote:
> On Mon, Jun 06, 2005 at 12:52:38PM +1000, Daniel Stone wrote:
> > To clarify: I deliberately broke everything Build-Depending on
> > xlibs-static-*.  The reasons are twofold: one, everything with PIC
> > patches for the misguided xlibs-static-pic needed to be transitioned;
> > two, it was good to get a clean cut, and I could engineer that within my
> > particular situation anyway.
> > 
> > While we've dug out most of the xlibs-static-* stuff now, I'm not sure I
> > can entirely recommend it for sid just yet.
> 
> Thanks for the explanation. That's the goal of coordinating fixes for
> packages while we're still in experimental. We don't have to catch
> everything, but a mail to -devel-announce about it, with maybe a list of
> the packages in Ubuntu that needed a fix would be good.

Sure, I can check this out, but the short summary is 'everything that
B-Ds on either xlibs-static-dev or xlibs-static-pic'. :)

There have also been a couple of other miscellaneous renames, including
xlibmesa-glu -> libglu1-xorg, xlibmesa-glu-dbg -> libglu1-dbg-xorg, and
xlibmesa-glu-dev -> libglu-dev-xorg (for the C++ ABI v2 transition).

> > The /usr/X11R6 -> /usr transition is definitely not sid-ready yet.  But
> > we've had no problems with the parts I've already transitioned to the
> > modular tree, excluding a couple of small catch-22s when building the
> > thing[0].
> 
> I'll defer to you and Josh and whoever else is getting deep with xlibs on
> this, but I really don't want to rock the boat on something like that until
> we know it'll work.

Sure.  I'm happy to sit out the pain in my little sandbox and see how
much, if any, pain it causes.  Right now, I'm still finding out issues
as I go (there's an unbelievable amount of stuff that hardcodes
/usr/foo/X11 and then installs to /usr/X11R6/foo/X11).

Attachment: signature.asc
Description: Digital signature


Reply to: