didier at slint.fr
Sat May 30 04:49:33 UTC 2020
Forwarding to the list as you answered privately to my first response.
The dependencies management optional feature of slapt-get/gslapt can
help only people having done a partial Slackware as if they did a full
one all dependencies are already met.
Further, this needs a reliable source of information about dependencies
included in PACKAGES.TXT.
For your information I maintain a distribution based on Slackware and
using slapt-get, called Slint. In slapt-getrc we include as source of
packages for Slackware this repository:
which has the dependencies documented in PACKAGES.TXT, courtesy of the
However Slint can do without this information for Slackware packages as
long as none is removed, as based on a full Slackware (only the KDE
series is optional). Further some packages are modified for Slint but
keep the same base and have priority over the genuine Slackware ones.
Additionally we do not support a partial Slint installation, so the
dependency information for Slint users only matters for packages that
are added to the Slint repository after the ISO has been published.
Slint users are advised if using build material from SBo to write a build
sqg -p <package>
and using it to build and install the packages and its dependencies but
always with the "keep" option:
sbopkg -k -i <package>
I also slightly modified sbopkg so that its "keep" option skips the
installed dependencies even if the full package name does not end in SBo
as we include several packages for which a SlackBuild is available @ SBo
but not at the same version or with the same content. Python3 comes to
mind: we ship version 3.5.9 but SBo currently has version 3.7.2 which
can lead to issues if /usr/bin/python3 links to a version that differ
from the one a given package that you try to run was built against.
All this rant to remind that the main difficulty with dependencies is
the accuracy of the list, which among many factors is context dependent,
the context including the build options for the packages and their
dependencies, their versions, and the installed software at time of
building the list.
Le 30/05/2020 à 02:01, Mark West a écrit :
> I asked because Vector Linux uses it i order to automate their packaging installation procedure and I think it would help to get more people interested in using Slackware 14.2 once they realize that they won't have to struggle trying to correctly install packages any more.
> On 5/29/20 6:06 PM, Didier Spaier wrote:
>> Le 29/05/2020 à 21:54, Mark West a écrit :
>>> Does Slackware 14.2 make use of GSlapt?
>> Slackware no indeed, but some Slackware users yes, as well as several
>> distributions based on Slackware. Some third party packages repositories
>> do include the information needed by slapt-get to manage dependencies as
>> e.G. sbrepos thanks to Eric Hameleers.
>> If you want to submit a SlackBuild for it @ SBo you'll have to do that
>> also for slapt-get of which GSlapt is a graphical front-end.
>> But I am not sure why you asked that, so if I misunderstood your
>> question please elaborate.
More information about the SlackBuilds-users