Peter Wullinger writes:

The planned system introduces a new link into the well-known
depencency hell already present on most open source unixoid
platforms, i.e. to compile package x I may need package y and must
not have installed package z, but not version a.b to version a.q of
it, because those are fundamentally broken (I think, everybody
who routinely compiles free software from source knows, what I'm
talking about).

That's only true if you're trying to hack stuff on your own, without the benefit of a packaging system. If you are using a package manager, all the dependency tracking will be taken care of.

I normally tend to compile non-system optional packages into
/opt/<package-name><package-version> and that introduces a
nice little shared library problem, when the linking stage does
not properly take care (or simply ignore) of -rpath's (like gtk
, glib and company. On the other hand, it makes proper package
versioning (and multiple installed versions of the same package)
possible, without introducing obscure cross-library version dependent
bugs.

You are trying to use the filesystem as a substitute for a functional package manager. A filesystem directory is not a suitable replacement for a package manager that correctly tracks dependencies.

The questions is: How much work would it be for you to still
(optionally?) bundle up the detached authlib in a extra
subdirectory within the normal source packages and modify
the configure script to check for an installed version of
the future authlib and use that (probably only, if it is newer),
if possible and setup the package up to build and install the
supplied one otherwise.

It's more work, simply because a lot of things are going to change within authlib when it becomes a separate package.

For starters, there will now be a single authdaemond binary. All authentication modules will now be shared libraries, dynamically loaded at runtime. You will still be able to build all authentication modules, but package LDAP, MySQL, and PostgreSQL shared libraries separately, because the configured authentication modules will be manually dlopen-ed, using libtool.

This will get rid of a lot of cruft in authlib.


Attachment: pgpB3ir1Aqvda.pgp
Description: PGP signature

Reply via email to