Hello, I'm new on this list. I plan to create a source package to build several binary packages (including shell functions, shell scripts, udev rules and documentation). This will be a Debian native package. My question is about the tarball, especially files taking place outside of the debian/ directory:
Is there best practice, implicit or explicit policy rules about the places where to put the files ? Can the directory trees reflect the paths files would have one time the binary packages will be installed on a system (for example: lib/bilibop/common.sh lib/bilibop/diskmap.sh lib/udev/bilibop_disk usr/bin/diskmap usr/share/initramfs-tools/hooks/bilibop-common usr/share/initramfs-tools/scripts/local-bottom/bilibop-lockfs etc.) or is it best to decrease path depth and even put as much files as possible at the root of the tarball ? Can I place them in arbitrary named directories or just shortcuts: bin/diskmap lib/bilibop_disk lib/common.sh lib/diskmap.sh initramfs-tools/bilibop-common initramfs-tools/bilibop-lockfs etc. or what ? Can I do as I want or have I to follow some good examples ? I have browsed some other tarballs with different conclusions, and read documentation, but never found something saying: "this is required" or more simply "this is a good way", "this is wrong, because..." or 'this is let at the discretion of the upstream developer". Is it the case ? Thanks in advance -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/n1r-kzt61kf...@safe-mail.net
