static libraries' policy
Christian.Iseli at licr.org
Christian.Iseli at licr.org
Fri Nov 11 23:56:58 UTC 2005
mpeters at mac.com said:
> They are extremely useful when compiling a piece of software that you intend
> to run on a different distribution.
I'm not so convinced. If that's really something you want to do: why not copy
the shared libs along with the application ?
> If you want to separate them out into a -static package that requires the
> -devel package, that's fine - but to just simply not include them will result
> in some developers switching to a distribution that allows THEM to decide
> whether or not to build software against a static library or not rather than
> imposing on them how they are to compile software.
I'm not against having -static packages, but I'm not sure it's worth the
trouble either.
I'm not against concerned developers having an %ifdef build_static in their
spec files. I just think it should be off by default.
I'd rather users think of Fedora as secure, sleek, fast, with some tendancy to
the cutting edge...
pertusus at free.fr said:
> I know some scientists and some sysadms (in labs, too ;-) that like to be
> able to do that.
It means they are tweaking packages anyway, and so should have no trouble
getting the static libs they might need.
Christian
More information about the fedora-extras-list
mailing list