What I was suggesting, is to let the user manage depencies himself.
This is what slackware users are used to do anyway.
It means that we should be able to provide an exhaustive list of needed packages on the command line.
As the semantic differ from the usual treatment of the PACKAGES arguments of supermin --prepare, this could be managed by a new option implying "do not search or install depencies for the given packages".
What do you think ?
Hi,
On Tuesday 11 November 2014 15:23:40 Mathieu Bouillaguet wrote:
> Hi Pino,
>
> Thanks for your reply and details.
>
> I started looking at the others package manager code and as I see it
> there is one main problem to port supermin to slackware distro.
>
> Slackware builtin package management tools (pkgtool and slackpkg) do
> not manage package dependencies. There is no easy solution to solve
> this problem.
> There are third party packet manager which manage dependencies but
> they are not supported and I don't personnaly use it.
>
> It would be possible to make supermin install only the packages
> entered on the command line by the user for slackware distro but
> maybe other tools rely on the package dependency installation
> semantic.
supermin relies on a package manager to provide the basic information,
including its dependencies and the list of its files. It needs such
information to be able to install in the supermin appliance that it
creates all the packages specified, including all of its dependencies
(recursively); this way it is possible to pull all the package needed,
making sure the appliance can run.
Imagine I want to build an appliance with bash, gcc, make, and a
library, so I can build in a clean environment with that library:
supermin needs to pick those packages in the appliance, together with
all the packages needed by those. That's how supermin works, basically.
If slackware does not provide basic package management like that, I'm
not sure how supermin is supposed to work.
--
Pino Toscano