ok, sound good.
Have you heard of that : https://help.launchpad.net/PPAQuickStart ?
I don't know if it can help.
August 30th is the deadline for new packages in Ubuntu 7.10
Moderator: Moderators
Yokozar, I'd like to push new versions of SpringLobby sources from my buildbot so that the deb packages get automatically generated in near-real time without anyone needing to manually do something for it. We need to discuss this.
Are you going to make both ubuntu and debian .debs for SpringLobby?
Oh and please report anything you need to fix to make it packageable, I'm happy to fix any non-standardness upstream.
Are you going to make both ubuntu and debian .debs for SpringLobby?
Oh and please report anything you need to fix to make it packageable, I'm happy to fix any non-standardness upstream.
This is actually doable via a script.semi wrote:Yokozar, I'd like to push new versions of SpringLobby sources from my buildbot so that the deb packages get automatically generated in near-real time without anyone needing to manually do something for it. We need to discuss this.
Code: Select all
cd (current package)
uupdate -u (new tarball) -v (new version)
cd ../spring-(new version)
dpkg-buildpackage -rfakeroot
There are a few things to watch out for, though. Because of all the bugs in Spring's scons build file (eg clean doesn't work), the package currently works around them by having a tarball within the source package and making an entire new folder. Unless we fix those scons bugs, you're going to have to modify the debian/rules part of the package to point to the new tarball each time, and you're also going to have to tar up the source tarball (so the "upstream" source is a tar within a tar).
Truthfully, though, there isn't much gained by this process. Only a handful of users will be using nightly debs anyway, and it's not too difficult for them to install by hand, and getting a script based on the above working just right would be alot of hackish effort. Methinks time would be better spent eliminating the needs for the hacks by fixing the scons bugs first.
Yes, it's not that hard.Are you going to make both ubuntu and debian .debs for SpringLobby?
Just the problems with scons. I'll try filing a bug in mantis soon - it was unable to register me last time I tried this a few weeks back.Oh and please report anything you need to fix to make it packageable, I'm happy to fix any non-standardness upstream.
SpringLobby is a separate project from Spring RTS. We build with autotools and the build system should be working pretty much the way it is meant to be used. We do not use scons at all. Our svn repo is on our own site. http://springlobby.info
I've nothing to do with scons bugs. So I hope you are making the lobby and the game engine separate debs?
Anyway, our project is progressing pretty fast, so nightly or just on-demand generation would be really nice.
I've nothing to do with scons bugs. So I hope you are making the lobby and the game engine separate debs?
Anyway, our project is progressing pretty fast, so nightly or just on-demand generation would be really nice.
To get back to the original topic, you can always get packages into Debian and *buntu as long as they follow the packaging standards and you find a sponsor to do a test and upload, for you.
Especially Debian unstable and testing do have some packages that are explicitly marked as software undergoing development. People installing these packages are aware that stuff might not work as expected. In my opinion, it would be good to get Spring into Debian asap as you will have more testers, that way.
If you need some contacts to people in Debian or *buntu, feel free to poke me. While I am not a DD nor a UD, I have contacts with both.
Especially Debian unstable and testing do have some packages that are explicitly marked as software undergoing development. People installing these packages are aware that stuff might not work as expected. In my opinion, it would be good to get Spring into Debian asap as you will have more testers, that way.
If you need some contacts to people in Debian or *buntu, feel free to poke me. While I am not a DD nor a UD, I have contacts with both.
Yeah, they will be separate.semi wrote:SpringLobby is a separate project from Spring RTS. We build with autotools and the build system should be working pretty much the way it is meant to be used. We do not use scons at all. Our svn repo is on our own site. http://springlobby.info
I've nothing to do with scons bugs. So I hope you are making the lobby and the game engine separate debs?
Honestly it's less of a hassle to just do it manually and push the new update to the server whenever I play SpringAnyway, our project is progressing pretty fast, so nightly or just on-demand generation would be really nice.
