[wpkg-users] [Bug 129] Out of stack space

[bugzilla-daemon at bugzilla.wpkg.org]

http://bugzilla.wpkg.org/show_bug.cgi?id=129


Rainer Meier <r.meier at wpkg.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME




--- Comment #4 from Rainer Meier <r.meier at wpkg.org>  2008-09-05 20:12:20 ---
I set this report to WORKSFORME as it seems not to be a problem of WPKG but a
problem of the package tree instead. I will investigate to include some code to
detect cyclic dependencies.

>if it has a dependency that is not met in the profile-file it should not
> install the package anyway, but skip the package where the dependency is not
> met, and log it. This way it will allways be clear what is installed. otherwise
> you could have a lot of software installed that is not listed in the
> profile-file.

Here I do not agree. Administrators do not want to add each dependency manually
to a profile even if the software is actually not directly used. For example I
use a package called "shortcut" - no user is using it on the workstation. But
it is used by some of my installer scripts - so the package depends on it.

The idea is that an administrator just needs to add a package to the profile
and WPKG takes care about the dependency tree. This is also the way most
dependency system work.

If it would not be the case then administrators would have to manually add
dependency packages (and dependencies of these dependencies) to the profiles.
If one of the packages gets its dependencies changed, then an administrator
would have to re-walk the whole dependency tree of all profiles. In addition it
would be much harder to find out if a package is just part of the profile
because another one is using it - or if it is really needed independently.
Especially if a dependency is removed after a while from a software package,
then it is hard to find out that a dependency package should be removed from
some profiles (probably not all of them).

The package system of all Linux package managers work exactly this way. If I
add Samba, then it will automatically install all required libraries.

One of the main advantages of the current algorithm is that if a dependency is
removed from a package at a later stage and the previously included package is
not included manually or listed as a dependency of another package, then WPKG
will remove this package since it is not needed at all. It is quite hard to do
this manually.


-- 
Configure bugmail: http://bugzilla.wpkg.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.