On 10.02.2015 18:07, Teemu Ikonen wrote: > Hi all, > > I built the ufoai packages from the pkg-games git repos. The resulting > packages work great as far as I've tested them and I hope you find a > sponsor for the packages soon. Hi, thanks for your kind words. I hope I will be accepted as Debian developer in the near future, so that I can upload the package myself at the latest. > > Building the thing from the git repo was a bit of a struggle though. > ufoai-music did not build out of the box because of directory mismatch > in the generated orig.tar. The attached patch to ufoai hopefully fixes > this. Thanks. I applied your patch already. > Overall, I'm not sure if storing just the debian dir in git is really > the way to go even with the data packages. Testing the build would be a > lot easier and take much less hd space if all the files would be already > present in the debian repos. Cloning the whole upstream git history, > creating the orig.tars and merging them to the repos containing debian > dirs could then be avoided. I once thought the same about big data packages and Git. However someone convinced me that it is more efficient for large data to store only the debian directory in the Git repository. Otherwise cloning the repos will take a long time. Git isn't very efficient when you have to store a lot of binary files. Besides as soon as ufoai is available on the official Debian mirrors, you can just use "apt-get source ufoai-data". Instead of cloning four separate repos, at the moment you only have to clone the upstream repository and download the "debian/rules" file from the ufoai source package. debian/rules get-orig-source debian/rules get-orig-ufoai-data works just fine. I use git-buildpackage with the following options: [git-buildpackage] tarball-dir = ../tarballs export-dir = ../build-area/ If you copy your ufoai tarballs to this tarball directory, you can build the package by switching to git master, which contains only the debian directory, and using "git-buildpackage". The tarball will automatically be picked up and used in this process. Regards, Markus
Attachment:
signature.asc
Description: OpenPGP digital signature