I would like to know the recommended path for creating a *.deb package (a C++ program), that depends on other C++ programs created by myself to be already installed on the system.

Is creating a package with the 2 projects a good idea? (How to do it?) or is a better idea to create different *.deb packages for every project?

migrated from serverfault.com Jun 15 '17 at 11:33

This question came from our site for system and network administrators.

  • 3
    It's better to create 2 deb packages and have A depend on B. – jordanm May 29 '17 at 4:59
  • 1
    There is no reason you can't have multiple related binaries in a single package, especially when installing one without the other won't make any sense. -|- Although from a maintenance perspective you might prefer to create separate packages which you can independently update and upgrade and then you use dependancy declarations syntax in your control files. – HBruijn May 29 '17 at 7:12
  • The question is rather vague, but it general, one should not create a binary Debian package which contains multiple unrelated software. – Faheem Mitha Jun 15 '17 at 11:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.