[Pkg-bitcoin-devel] Some packaging questions

[Scott Howard]

On Mon, Oct 27, 2014 at 2:11 PM, Shawn Djernes <sdjernes at gmail.com> wrote:
> This stuff may be documented, but I am not sure how to phrase the
> Google searches.
>
> I am working on packaging MinePeon.

Great! Thank you.

> 1.  The UI package which will be able to be Architecture: all. Has
> nothing to "make". It contains a bunch of PHP that needs to go into
> somewhere, some cron jobs, and some directories that need to be made.
>
> A. Is their a documented way to do this type of package, or someone
> know an example package I can tear apart and read?

Example:
http://stackoverflow.com/questions/3214319/i-need-my-debian-rules-file-to-simply-copy-files-to-its-target
Also see:
https://www.debian.org/doc/manuals/maint-guide/
use the standard short "debian/rules" and just add just make a
"packagename.install" file that tells what should be installed where.

> B. I want it to all be owner minepeone group www-data so that the web
> server can make changes to it's files.

See:
https://www.debian.org/doc/debian-policy/ch-files.html#s-permissions-owners
Also, if you want your package in Debian, make sure you follow all of
the policies in that policy guide.

> C. As far as I can tell it has no "build" dependencies because it is
> not being built. So what do I put in this line?

I suggest using simple dh rules for your package since it sounds quite
basic. In that case you shouldn't have any explicit build target in
debian/rules.
You can also override targets, see:
https://joeyh.name/blog/entry/debhelper_dh_overrides/

https://www.debian.org/doc/manuals/maint-guide/ is a great starting
point for packaging.

~Scott