What makes Checkinstall packages not suitable for distribution?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
2
down vote

favorite












I am planning to have multiple servers running with the same packages. And as a solution to not compile packages individually on each server, I want to use checkinstall to generate .deb and then distribute it via private repository.



However, in the linked guide it says that it is




not designed to produce packages suitable for distribution




My questions are:



  1. What is different about this packaging, that makes it not suitable for distribution? Or what should be in the package, to make it suitable?


  2. Could there be any issues with using checkinstall and distributing packages to ~20 servers?


Any advice or links where I can find out more appreciated. Thanks!










share|improve this question

























    up vote
    2
    down vote

    favorite












    I am planning to have multiple servers running with the same packages. And as a solution to not compile packages individually on each server, I want to use checkinstall to generate .deb and then distribute it via private repository.



    However, in the linked guide it says that it is




    not designed to produce packages suitable for distribution




    My questions are:



    1. What is different about this packaging, that makes it not suitable for distribution? Or what should be in the package, to make it suitable?


    2. Could there be any issues with using checkinstall and distributing packages to ~20 servers?


    Any advice or links where I can find out more appreciated. Thanks!










    share|improve this question























      up vote
      2
      down vote

      favorite









      up vote
      2
      down vote

      favorite











      I am planning to have multiple servers running with the same packages. And as a solution to not compile packages individually on each server, I want to use checkinstall to generate .deb and then distribute it via private repository.



      However, in the linked guide it says that it is




      not designed to produce packages suitable for distribution




      My questions are:



      1. What is different about this packaging, that makes it not suitable for distribution? Or what should be in the package, to make it suitable?


      2. Could there be any issues with using checkinstall and distributing packages to ~20 servers?


      Any advice or links where I can find out more appreciated. Thanks!










      share|improve this question













      I am planning to have multiple servers running with the same packages. And as a solution to not compile packages individually on each server, I want to use checkinstall to generate .deb and then distribute it via private repository.



      However, in the linked guide it says that it is




      not designed to produce packages suitable for distribution




      My questions are:



      1. What is different about this packaging, that makes it not suitable for distribution? Or what should be in the package, to make it suitable?


      2. Could there be any issues with using checkinstall and distributing packages to ~20 servers?


      Any advice or links where I can find out more appreciated. Thanks!







      apt package-management packaging checkinstall






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 6 at 13:56









      Ilya

      1235




      1235




















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          4
          down vote



          accepted










          Packages created by checkinstall often don't meet the standards for packages. This may cause problems if you distribute a package to other people. But there's nothing wrong if you use them on multiple of your own systems if they work for you.



          For example packages created by checkinstall usually don't contain dependency information so they may not work until you manually install some additional packages.



          Some files may be placed in a wrong location, have a wrong name or reference files with a wrong location or wrong name. They may for example not work with they way Debian and Ubuntu handle the Apache configuration or the system startup without some additional work.






          share|improve this answer




















          • Hey, thanks for replying. Indeed the packages didn't handle any dependencies and I had to manually install.
            – Ilya
            Feb 7 at 4:52










          Your Answer







          StackExchange.ready(function()
          var channelOptions =
          tags: "".split(" "),
          id: "89"
          ;
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function()
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled)
          StackExchange.using("snippets", function()
          createEditor();
          );

          else
          createEditor();

          );

          function createEditor()
          StackExchange.prepareEditor(
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: false,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          );



          );













           

          draft saved


          draft discarded


















          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1003556%2fwhat-makes-checkinstall-packages-not-suitable-for-distribution%23new-answer', 'question_page');

          );

          Post as a guest






























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          4
          down vote



          accepted










          Packages created by checkinstall often don't meet the standards for packages. This may cause problems if you distribute a package to other people. But there's nothing wrong if you use them on multiple of your own systems if they work for you.



          For example packages created by checkinstall usually don't contain dependency information so they may not work until you manually install some additional packages.



          Some files may be placed in a wrong location, have a wrong name or reference files with a wrong location or wrong name. They may for example not work with they way Debian and Ubuntu handle the Apache configuration or the system startup without some additional work.






          share|improve this answer




















          • Hey, thanks for replying. Indeed the packages didn't handle any dependencies and I had to manually install.
            – Ilya
            Feb 7 at 4:52














          up vote
          4
          down vote



          accepted










          Packages created by checkinstall often don't meet the standards for packages. This may cause problems if you distribute a package to other people. But there's nothing wrong if you use them on multiple of your own systems if they work for you.



          For example packages created by checkinstall usually don't contain dependency information so they may not work until you manually install some additional packages.



          Some files may be placed in a wrong location, have a wrong name or reference files with a wrong location or wrong name. They may for example not work with they way Debian and Ubuntu handle the Apache configuration or the system startup without some additional work.






          share|improve this answer




















          • Hey, thanks for replying. Indeed the packages didn't handle any dependencies and I had to manually install.
            – Ilya
            Feb 7 at 4:52












          up vote
          4
          down vote



          accepted







          up vote
          4
          down vote



          accepted






          Packages created by checkinstall often don't meet the standards for packages. This may cause problems if you distribute a package to other people. But there's nothing wrong if you use them on multiple of your own systems if they work for you.



          For example packages created by checkinstall usually don't contain dependency information so they may not work until you manually install some additional packages.



          Some files may be placed in a wrong location, have a wrong name or reference files with a wrong location or wrong name. They may for example not work with they way Debian and Ubuntu handle the Apache configuration or the system startup without some additional work.






          share|improve this answer












          Packages created by checkinstall often don't meet the standards for packages. This may cause problems if you distribute a package to other people. But there's nothing wrong if you use them on multiple of your own systems if they work for you.



          For example packages created by checkinstall usually don't contain dependency information so they may not work until you manually install some additional packages.



          Some files may be placed in a wrong location, have a wrong name or reference files with a wrong location or wrong name. They may for example not work with they way Debian and Ubuntu handle the Apache configuration or the system startup without some additional work.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 6 at 14:57









          Florian Diesch

          63.1k16157176




          63.1k16157176











          • Hey, thanks for replying. Indeed the packages didn't handle any dependencies and I had to manually install.
            – Ilya
            Feb 7 at 4:52
















          • Hey, thanks for replying. Indeed the packages didn't handle any dependencies and I had to manually install.
            – Ilya
            Feb 7 at 4:52















          Hey, thanks for replying. Indeed the packages didn't handle any dependencies and I had to manually install.
          – Ilya
          Feb 7 at 4:52




          Hey, thanks for replying. Indeed the packages didn't handle any dependencies and I had to manually install.
          – Ilya
          Feb 7 at 4:52

















           

          draft saved


          draft discarded















































           


          draft saved


          draft discarded














          StackExchange.ready(
          function ()
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1003556%2fwhat-makes-checkinstall-packages-not-suitable-for-distribution%23new-answer', 'question_page');

          );

          Post as a guest













































































          Popular posts from this blog

          pylint3 and pip3 broken

          Missing snmpget and snmpwalk

          How to enroll fingerprints to Ubuntu 17.10 with VFS491