No, I have not, but I suggest that a "one size fits all" approach is going to be harder that you imagine. Especially if you are compiling with FPC, have extra units you need, want to make a src package....
Making a binary is easy, in very simplified terms, you build a directory (I call it BUILD) containing the things you want to appear on the user's system. You then run something like -
fakeroot dpkg-deb -b BUILD/. myapp_amd64.deb <enter>
In practice that will probably have a lot of lintian errors but will probably work fine.
Building a SRC package to submit to debian is a bit harder, it has to (later) build (from src package to binary package) with make and those lintian errors I mentioned will have the debian people shaking their heads. But all that can be fixed and scripted if you are willing to put a bit of effort in.
Here is my script to build debian and rpm binary packages for amd64, i386 and raspi (along with a kit to package a windows installer) -
https://github.com/tomboy-notes/tomboy-ng/blob/master/package/package.bashIts probably far more complicated that you need initially but look into the methods inside.
Here is a my doc of my method of building a SRC a package that I routinely submit to Debian (v0.36 accepted into unstable today) -
https://github.com/tomboy-notes/tomboy-ng/blob/master/prepare.mdIn both cases, most certainly NOT scripts you can use because they are setup for my particular project. But you can easily pick out the bits you want, modify them accordingly and discard the remainder.
Davo
Recent
