UFO:Alien Invasion

Technical support => Linux => Topic started by: oggei on August 23, 2010, 07:50:18 pm

Title: ufoai 2.3 32bit debian (mostly sid) packages
Post by: oggei on August 23, 2010, 07:50:18 pm
Hi, just want to let to know who cares that i compiled and uploaded on my public machine 2.3 packages for 32bit arch.

Packages are at https://www.scimmia.net/~aogier/ufoai

thank you, ufoai is great, cheers :)
Title: Re: ufoai 2.3 32bit debian (mostly sid) packages
Post by: Mattn on August 23, 2010, 11:48:49 pm
how did you solve this error: http://sourceforge.net/tracker/?func=detail&aid=3018406&group_id=157793&atid=805242 ?
Title: Re: ufoai 2.3 32bit debian (mostly sid) packages
Post by: oggei on August 24, 2010, 09:27:00 am
how did you solve this error: http://sourceforge.net/tracker/?func=detail&aid=3018406&group_id=157793&atid=805242 ?

As this dependency, at least in 2.3 tag, is a direct (correct) consequence of ${shlibs:Depends} and not a standard requires item, and i'm not having nvidia hw, i just compiled package and this resulted in

Depends: [...], libgl1-mesa-glx | libgl1, [...]

I suggest to slightly change debianization, splitting binary packages in eg. ufoai-nvidia, ufoai-intel, letting users to choose which binary is best suited for his needs. The split have to be in configure invocation, not in hardcoded depends lines imo.

I eventually can spend some spare time on this, probably this weekend


cheers,
Title: Re: ufoai 2.3 32bit debian (mostly sid) packages
Post by: Mattn on August 24, 2010, 09:42:18 am
i don't think we should create different packages for different cards here - maybe i should just build the packages in a chroot env to ensure that no nvidia-current is installed there.
Title: Re: ufoai 2.3 32bit debian (mostly sid) packages
Post by: oggei on August 24, 2010, 09:48:45 am
i don't think we should create different packages for different cards here - maybe i should just build the packages in a chroot env to ensure that no nvidia-current is installed there.

As i don't exactly know how much glx-dev packages are available (afaik it's usually only mesa_generic/nvidia split), building packages in a eg. pbuilder env is indeed always the right thing to do.
I would anyway like to suggests not to drop nvidia ppl as well, but that's ur biz anyway :)


thanks, cheers,