sauerbraten srpm???

[ghostbunny]

Hi guys,

i would like to update sauerbraten but i can't find the srpm or at least a spec file from pclos but it is already in the repo.
i searched the megagames repo on the up to date nluug and vim server also the main section on nluug and i can't find anything. also rpmphobe and rpmseek doesn't list our package.

if anyone has more information, please let me know. if we don't find it i'll try to reinvent the wheel 

[MBantz]

Hi ghostbunny,

I packaged sauerbraten once, let me see if the srpms or specfile is still available on my system,

it's quite large, guess this is the reason it's not stored online,

cheers,
MBantz

[ghostbunny]

Hi ghostbunny,

I packaged sauerbraten once, let me see if the srpms or specfile is still available on my system,

it's quite large, guess this is the reason it's not stored online,

cheers,
MBantz

Thanks, i wish you the best to find it.


[offtopic=on]
A general suggestion: If the srpm is to big for storing could we store at least a archive with the spec and all used extra data (patches, icons, desktop file...) to prevent such situations?
[offtopic=off]

[MBantz]

Hi ghostbunny,

I packaged sauerbraten once, let me see if the srpms or specfile is still available on my system,

it's quite large, guess this is the reason it's not stored online,

cheers,
MBantz

Thanks, i wish you the best to find it.


[offtopic=on]
A general suggestion: If the srpm is to big for storing could we store at least a archive with the spec and all used extra data (patches, icons, desktop file...) to prevent such situations?
[offtopic=off]

+1 for that :-)

specs from 2009 here: http://dl.dropbox.com/u/2546717/sb.tar.xz

[MBantz]

an alternative way of packaging these monsterrpm's could be this idea I had once,

this is a src.rpm of only 14kbytes of alienarena:
http://dl.dropbox.com/u/2546717/alienarena-7.51-1MBantz2010.nosrc.rpm

the idea is to let the user get the data files when installing the rpm,

it didn't catch on at that time though,

cheers,
MBantz

[ghostbunny]

Thanks Martin

an alternative way of packaging these monsterrpm's could be this idea I had once,

this is a src.rpm of only 14kbytes of alienarena:
http://dl.dropbox.com/u/2546717/alienarena-7.51-1MBantz2010.nosrc.rpm

the idea is to let the user get the data files when installing the rpm,

it didn't catch on at that time though,

cheers,
MBantz

that's seems to be a good solution also but you will need separate source and data downloads. in this case everything is in one single tarball. Data, pre compiled binaries and the source code including some static libraries for the binaries. So you have to download everything just for the data. i'll try to merge the three specs because everything is built from this single tarball and it would be wasting space to create a single srpm for server, client and data. so we will have just one srpm with around 560mb instead of three.

regards
ghostbunny

[MBantz]

Thanks Martin

an alternative way of packaging these monsterrpm's could be this idea I had once,

this is a src.rpm of only 14kbytes of alienarena:
http://dl.dropbox.com/u/2546717/alienarena-7.51-1MBantz2010.nosrc.rpm

the idea is to let the user get the data files when installing the rpm,

it didn't catch on at that time though,

cheers,
MBantz

that's seems to be a good solution also but you will need separate source and data downloads. in this case everything is in one single tarball. Data, pre compiled binaries and the source code including some static libraries for the binaries. So you have to download everything just for the data. i'll try to merge the three specs because everything is built from this single tarball and it would be wasting space to create a single srpm for server, client and data. so we will have just one srpm with around 560mb instead of three.

regards
ghostbunny

Well, when packaging large rpm's it's tedious to fix a spec up when hundreds of issues can arise. That's why I keep data and program separate. Flightgear for instance was hours to compile, just to realise some small error in the desktop file or something :-) Now it has a separate data and program spec.

Adding ccache to a large compile, makes a build even more efficient.

To make sure the best packaging is performed with smallest amount of time, I recommend to keep program and data separate. The server spec is perhaps small enough to merge with the program spec,

may the force be with you :-)

cheers
MBantz