Slashdot Mirror


How to Make Easy-to-Package Software, Part 2

jmmv writes "A month ago (more or less), the first part of the Making packager-friendly software was published and announced here; it seemed to be warmly accepted by the community. Now it's the turn for the second (and last) part, which has just seen the light. It deals with problems caused by recursive dependencies, configuration file handling, unprivileged builds, the make utility, build infrastructure oddities and some notes about code portability. Of course, these are just suggestions to try to make the life of packagers a bit simpler; you can just ignore them if you want to. I hope it will be of interest and that future versions of your creations are easier to package. Thanks!"

2 of 13 comments (clear)

  1. Installers by Umbral+Blot · · Score: 4, Insightful

    You have to admit, no matter how much you like Linux, that both windows and mac have done a much better job with their installers. I can whip up an installer in a few minutes on windows that I am confident will work on everyone's machine, but this is unfortunately not true in Linux.

  2. Yes but what will your installer *break*? by leonbrooks · · Score: 3, Insightful

    For a self-contained YAKoSoSBP<*>, no worries, but for anything serious you have to futz around lots to avoid DLL collisions and registry slapdown games. On Linux or BSD, I just put in the dependencies and let URPMI/yum/apt/YAST sort it out. Different versions of shared libraries are delighted to coexist, BoC you don't need to do that, see below.

    Anyway, why do you need to ship an installer at all, isn't the OS supposed to provide that kind of plumbing? And what happens when the user gets to WinCE on ARM or something like that? I can post a .src.rpm for people whose distros or architectures I haven't explicitly packaged for, can you? The .src.rpm also allows seamless integration with systems running on odd versions of shardd libraries, one simply does a wone-liner (or one-click) rebuild of the offending .src.rpm and viola, all dependencies solved.

    <*> YAKoSoSBP == Yet Another Kind of Solitaire or Sliding Block Puzzle

    --
    Got time? Spend some of it coding or testing