[haiku-development] Re: Removing /boot/common
- From: Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 7 Oct 2013 10:51:50 +0200 (CEST)
> On October 7, 2013 at 2:10 AM Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> Git was just an example of a software where this kind of dependency is
> not obvious to see. Pretty much any software which we split into
> different packages may have such a dependency. ATM this is true for all
> devel packages, since they use a relative symlink. This should be
> relatively easy to change, though I'm not so sure about the *-config
> scripts, pkgconfig and libtool files they contain.
Sounds like tedious work in any case.
> I read this paragraph a few times, but I'm afraid I still don't
> understand the question.
Sorry, I try again:
1) assume a package that is divided into several packages, where one of them is
installed in system (let's call it A, the other package would be B).
2) you want to install B, but in common.
3) B does not declare a dependency to A but to common-A IOW it declares the need
to find its sister package in the same installation path.
4) common-A shadows A.
5) everything continues to work with the downside that you now have A and
common-A installed.
That would be a compromise as well, but if this is a rare case, I guess it could
be acceptable.
> Sure. Regarding find_directory(), as we know now, it isn't a
> particularly good API. It failed with both the introduction of the
> non-packaged hierarchies and the removal of /boot/common.
Okay, let's call it the concept of find_directory() then :-)
Have you already thought of an extension to that API?
Bye,
Axel.
Other related posts:
