Re: Packaging (was Re: Socket library?)
- From: Simon Heath <icefoxen@xxxxxxxxx>
- To: luajit <luajit@xxxxxxxxxxxxx>
- Date: Thu, 04 Oct 2012 16:04:44 -0700
Excerpts from Francesco Abbate's message of 2012-10-04 13:52:43 -0700:
> Not quite agree with you. When you develop a project you can produce a
> debian package but you don't have too. The idea is that interested
> people can compile it and the debian package can be created by the
> community usually by people experienced in package creation.
Okay, that's a good point. I got a little more foaming-at-the-mouth
on this point than I really intended, and completely ignored this
possibility. :-)
> For the other side I agree with you about the convenience of having
> debian packages for libraries. I also use standard packages for all
> the libraries I need when I'm on linux and this is definitely a good
> thing. This is the big advantage on Linux compared to Windows, its
> packaging system is great and there isn't anything similar on Windows.
> But the point is that packages are useless if you want to embed a
> software in your project. So my comment about luajit2 since it will be
> often used to be embedded in a product instead of as a library.
I'm not sure I understand your distinction between 'library' and
'embedded in a product'. Are you referring to it being statically
linked as part of a bigger binary, or even having most of a project
written using a particular version of luajit as a core component?
If that is the case... I would still rather use the Debian package
of luajit if possible: it provides a static library to link with,
it handles updates and such for me, and has probably been bug-tested
harder than average. Of course that's not always practical, and comes
with its own downsides: I vividly recall Debian being stuck on an old,
semi-broken version of qemu for about a year and a half...
> Sorry but software that needs to be compiled is not junk.
No, of course not. But _forcing_ me to compile something by hand when
a machine could be doing it for me in an automated, consistent fashion
and providing me with the result _is_ junk. I suppose if I care that
strongly about it, then I should care enough to become a package
maintainer myself.
;-)
Simon
Other related posts:
