From: Joost Y. D. <jo...@lu...> - 2004-07-28 07:03:59
|
> Customization by packagers is not really the issue: they can use custom.mk and > put all the files in the right location for their distribution. What I would > like, is to be able to make a mostly statically compiled openMSX for Linux > that only depends on widely available libs such as glibc and Xlib. It would > be nice if a user could install such a binary in any location he likes. I personally don't consider this a very important goal. I think it's much easier to just integrate packaging for the major distros into openMSX CVS and just release next to the source a bunch of packages. This can all be automated. It is just a boring job that has to be done. > I'm not sure a hybrid solution is better than a single-approach solution. At > least a single-approach solution has the advantage that it is easy to explain > and understand. I agree. > On Tuesday 27 July 2004 19:03, Bas Wijnen wrote: > > As far as I know the usual way to solve this problem is with a configure > > script (which can, but does not need to be, made by autoconf.) > > I'm very glad I got rid of autoconf/automake, I certainly don't want them > back... ;) Even though I have not looked at your new system in detail yet, I fully agree on this. Joost |