Re: New tazpkg installs busybox-pam for tazpkg

[GoKhlaYeh <gokhlayeh@xxxxxxxxxx>]

Hi Christopher (and all),

After some checks it appears that tazpkg-4.1.1 have the same behavior: this is not related to my last changes.

Here's a precise description of what's happens :
* When you install tazpkg, it checks for depends; depends include busybox.
* As you have pam installed (I'm sure you have), and as busybox-pam provide busybox when pam is installed, it uses the depend busybox-pam instead of busybox.
* As busybox-pam is not installed, it installs it even if busybox (legacy) was already installed.

So, the question is : is it a bug or a feature ?
This behavior is quite logical (tazpkg is configured with auto_install_depends on) and doesn't screw you're system. About this particular case, having busybox-pam overwriting busybox when pam is installed looks like a feature. In an other hand, if you remove pam, or busybox-pam, you'll screw you're system as there will be no more commons tool to re-install busybox properly; but in fact this is another point.

* About tazpkg & provide system :
provide handle some different cases, so disable the feature described above will lead to some **real** problems :
- what about packages needed apache, if apache doesn't install because lighttpd is already here ?
- same with perl/microperl; lzma/xz and some others.

Hope this help to understand better whats going on.

On Fri, 10 Dec 2010 15:54:29 +0000
Christopher Rogers <slaxemulator@xxxxxxxxx> wrote:

> The new tazpkg is installing busybox-pam as a depend. Its also saying there
> is a depend loop with busybox-pam-1.17.4 and busybox-pam.
> 
> Pastebin of my tazpkg log below: $(I got the log doing tazpkg get-install
> tazpkg > tazpkg.log in shell)
> 
> http://pastebin.com/7kmqWzEK
> 
> I think this commit cause the problem:
> 
> http://hg.slitaz.org/tazpkg/rev/6f594569d967
> 
> I hope this helps.


-- 
GoKhlaYeh <gokhlayeh@xxxxxxxxxx>


---
SliTaz GNU/Linux Mailing list - http://www.slitaz.org/