[haiku-development] Re: What for does SAT solver needed for package management?
- From: "X512" <danger_mail@xxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 19 Jun 2012 10:23:59 +0400
On Mon, 18 Jun 2012 21:56:27 -0500, Joseph Groover <looncraz@xxxxxxxxxxx>
wrote:
> Not only that, but a more 'finessed' solution could be introduced
> later. Implement a fat-binary system (or just copy the dependents
> into
> the app's lib folder) now, something better later.
>
> Also, a hash could be made of each shared library and you could just
> symlink them together - gaining most/all the efficiency benefits at
> the
> same time.
>
> Maybe two package types: Fat (comes with all dependencies - static or
> dynamic, either way), Slim (comes with no external dependencies, but
> has
> a simple list of dependencies which can be user-resolved). Later on,
> automatically resolving those dependencies can be worked out.
>
> I like it! +1
>
> --The loon
I think that fat/slim binary system is unnecessary. Every application
depends on OS. If developer want, he can add additional dependencies,
if don't he don't add. In some cases application can't be bundled:
application can use servers(applications, that are running in background
an process requests), that are used by other applications.
User should have ability to download application and dependencies
manually without any repositories. Repositories and automatic
dependency resolving should be just additional helpful tools, not a
must have tools for installation.
To Haiku developers:
How Haiku package depedencies will be integrated? Can package component
collision occur? For example packages A and B provides diffrent and
incompatiable libsys.so. Package C use libsys.so from package A and
package D use libsys.so from package B. Will this work well?
Also what happens if package both A and B have independent private
library libruntime.so? Can packages use their own libruntime.so?
Other related posts:
