Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to create a Debian package that runs a few scripts in postinst. These scripts are only needed in postinst (they're just too unwieldy to include in postinst itself).

Is there a standard way to have them included and accessible in the installation process and then discarded, or should I simply put them in /usr/share/package-name/ and run them from there?

I decided to put the scripts in /usr/share/package-name/ and run them there, but I'm still interested in an answer to the question.

share|improve this question
up vote 3 down vote accepted

/usr/share/package-name/ is the way to go; packages are made of control files and content and nothing else.

The really complicated setups like exim4-config, ldap-auth-config and krb5-config get their own packages to hold configuration scripts and semi-generated conffiles. Things like ebox are also in large part configuration generators.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.