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

Re: Feature Freeze



On Tue, Oct 10, 2006 at 02:35:05PM +1000, Drew Parsons wrote:
> This page will work well I think.  I'll keep updating the input drivers
> bit by bit until they're all done, and will mark them as "frozen" on
> the wiki when done.

Awesome. I'll be doing the same.

> I've been gauging package state by the version table on
> http://qa.debian.org/developer.php?login=debian-x@lists.debian.org A
> couple of libs seem to have dropped through the cracks: libxres to be
> precise. There is a minor update for libxau located upstream, as well
> as libXScreenSaver, which I suppose we should include. I didn't touch
> libXScreenSaver previously because I wasn't sure how best to manage it
> in regards to libxss. Keep the old name? Update to the new?

The minor updates are fine, although they don't really seem to be
worthwhile iirc, since they basically just allow you to run lint during
builds, which isn't interesting to us. If you want to do the update though,
go for it. 

As for xss, I say we leave the package name as it is for etch and then fix
it later. Changing the package name this late in the game doesn't really
buy us anything interesting. I'd be happy to have it be one of those
instant changes we make once etch is out though.

> I'm interested in packaging the developmental i810 (intel) modesetting
> branch. Alan is keen for people to test it. I'd think to call the new
> package xserver-xorg-video-intel, since I think X.org upstream will be
> calling it "intel" once it's finally released.  I'd put lots of "this
> driver is a development snapshot, only use it if you really mean it"
> warnings into the description.

I'm not sure renaming the driver is a good move right now. I don't want to
jump the gun on upstream. I also don't want people who will inevitably fail
to read the warning to install it thinking that it's the only intel video
driver when they should be using the i810 package. Admittedly,
xserver-xorg-video-i810-modesetting is a mouthful, so if there's a
compromise in there somewhere that'd probably be ideal. I'd like to see the
driver in the archive too though, so if you don't beat me to it I'll try
and jump on this as well.

 - David Nusinow



Reply to: