Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Jheengut Pritvi]

On 19 Feb 2018 12:47 am, "Didier Spaier"  wrote:

Le 18/02/2018 à 21:19, B Watson a écrit :
> On 2/18/18, Didier Spaier  wrote:
>>>
>>> When installing software, if a package is available through slapt-get,
>>> it will install it, otherwise it will install it through slapt-src. If
>>> any SlackBuild dependencies are available through slapt-get, it will
>>> install them through slapt-get.
>
> This sounds like a recipe for disaster.

Possibly,indeed, it it's misused.

> SBo packages are tested with
> dependencies from SBo, this thing would install binaries from elsewhere if
> it can find them?

>From elsewhere but not from anywhere.

I did my best to warn at least the Slint users, cf.
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-
get/slapt-getrc.x86_64
which links to:
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-
get/README.slaptgetrc.Slint

But have all users read the docs won't happen, I know...

> Right now there's a guy on IRC complaining that alienbob's vlc package
> segfaults, and it turns out to be because he's using SBo's qt5 instead
> of alienbob's. Mixing and matching repos is the cause, in other words.

Yes. Incidentally that's why I ended up including in the Slint repo a
vlc-2.2.8 package built against qt4, using Eric's SlackBuild.

Cheers, Didier
___



I will look into the slapt-xxx,

Cheers Pritvi
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Petar Petrov]

heh... i really wish CRUX's prt-get could work with SBo

https://crux.nu/doc/prt-get%20-%20User%20Manual.html

2018-02-16 10:29 GMT+02:00 Jheengut Pritvi :
> With the forthcoming of Slackware 15.0, I have been nostalgic of the
> days when I tried crazy thing with my Slackbox. One of those was using
> BSD's ports and portage within Slackware. It was a succees and a
> failure too. In those times, I was not using slackbuilds.org.
> The big question:::
> Is it worthwhile for a ports/portage/pacman like package manager for
> Slackware that manages both binary and source packages?
>
>
> It could be tool on top of pkgtool and sbopkg.
>
> What is your opinion?
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Didier Spaier]

Le 18/02/2018 à 21:19, B Watson a écrit :
> On 2/18/18, Didier Spaier  wrote:
>>>
>>> When installing software, if a package is available through slapt-get,
>>> it will install it, otherwise it will install it through slapt-src. If
>>> any SlackBuild dependencies are available through slapt-get, it will
>>> install them through slapt-get.
> 
> This sounds like a recipe for disaster.

Possibly,indeed, it it's misused. 

> SBo packages are tested with
> dependencies from SBo, this thing would install binaries from elsewhere if
> it can find them?

From elsewhere but not from anywhere.

I did my best to warn at least the Slint users, cf.
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-get/slapt-getrc.x86_64
which links to:
http://slackware.uk/slint/x86_64/slint-14.2.1/source/slapt-get/README.slaptgetrc.Slint

But have all users read the docs won't happen, I know...
 
> Right now there's a guy on IRC complaining that alienbob's vlc package
> segfaults, and it turns out to be because he's using SBo's qt5 instead
> of alienbob's. Mixing and matching repos is the cause, in other words.

Yes. Incidentally that's why I ended up including in the Slint repo a
vlc-2.2.8 package built against qt4, using Eric's SlackBuild.

Cheers, Didier
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[B Watson]

On 2/18/18, Didier Spaier  wrote:
>>
>> When installing software, if a package is available through slapt-get,
>> it will install it, otherwise it will install it through slapt-src. If
>> any SlackBuild dependencies are available through slapt-get, it will
>> install them through slapt-get.

This sounds like a recipe for disaster. SBo packages are tested with
dependencies from SBo, this thing would install binaries from elsewhere if
it can find them?

Right now there's a guy on IRC complaining that alienbob's vlc package
segfaults, and it turns out to be because he's using SBo's qt5 instead
of alienbob's. Mixing and matching repos is the cause, in other words.
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Didier Spaier]

Hello,

Le 18/02/2018 à 10:52, Jheengut Pritvi a écrit :
<>> My supposition  is the ability to manage packages from a singular
> command from maybe multiple binary repo and source repo.
> 
> 
> Slackware is meant to be installed as a whole.
> What if you want the simplicity of Slackware and the ability to
> install a small base along with with a few other packages and optimize
> it with reduced dependencies for new packages. This is a lot to ask,
> other distro offer some of these options but gives you too much
> overhead and headache.
> 
> The answer might lie in using something else, I am unable to put it in 
> words,..

A possible answer is spi from George Vlahavas:
https://github.com/gapan/spi

From the README:

> spi (Salix Package Installer) is a command line tool that acts as a
> wrapper around slapt-get and slapt-src.
>
> It searches both package (slapt-get) and SlackBuild (slapt-get) local
> caches for software. It can also update both local caches.
>
> When installing software, if a package is available through slapt-get,
> it will install it, otherwise it will install it through slapt-src. If
> any SlackBuild dependencies are available through slapt-get, it will
> install them through slapt-get.

slap-src, slapt-get, their GUIs gslapt and sourcery and spi are included
in Salix, Slackel and Slint and usable on Slackware. All command-line
tools have associated man pages.

Several packages repositories can be used with priorities and automatic
dependencies management is provided and optional. Usual caveat for these
features: know what you are doing and be aware of the limitations of the
tools.

If you want to begin with a small base (as do Salix and Slackel) you
will need dependency information about genuine Slackware packages.
To do that, just include as SOURCE in /etc/slapt-get/slapt-getrc e.g.
this repository: http://slackware.uk/salix/x86_64/slackware-14.2/
as George has computed the deps listed in PACKAGES.TXT in the PACKAGE
REQUIRED field.

Some other repos also provided this information as e.g. the repositories
sbrepos kindly provided by Eric:
http://slackware.uk/people/alien/sbrepos/

Be aware though that deps can vary upon the environment in which the
package has been built. For instance sbrepos assume a full Slackware
installation hence only list dependencies beyond that.

And in case anyone wonders: this post is *not* a request to include
these tools in Slackware.

Have a good day,

Didier
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Jheengut Pritvi]

On 16 February 2018 at 12:29, Jheengut Pritvi  wrote:

> The big question:::
> Is it worthwhile for a ports/portage/pacman like package manager for
> Slackware that manages both binary and source packages?
>
>
> It could be tool on top of pkgtool and sbopkg.


On 18 February 2018 at 11:37, B Watson  wrote:
> On 2/18/18, Jheengut Pritvi  wrote:
>> But pkgsrc does not use the slackbuilds.org Slackbuilds to build packages.
>


> Have you looked at sbotools? It's at least somewhat similar to
> ports/pkgsrc (or anyway it's been described to me that way, I haven't
> actually used it).
>

Sbotools provide a big overhead in providing dependency resolution in
the form of  handling of requirements from a slackbuild’s .info file,

I am looking forward for something that can manage packages from both
Slackware and slackbuilds.org.
Slackpkg+ deals with multiple online/offline repositories.

Slax used to build a Live ISO from Slackbuilds from the Slackware Source repo.

In the long run, I am projecting to alleviate between building
packages from scratch like gentoo for an optimized built for my
SlackBoxes,
for testing purposes.


> If you google for Slackware + pkgsrc, you probably will find an ancient
> set of directions that you should *not* follow (it involves replacing
> most of the OS with pkgsrc equivalents, and "rm -rf /var/log/packages"
> is one of the steps in the procedure...)

I tried it along time back and still not fancy it that much.


My supposition  is the ability to manage packages from a singular
command from maybe multiple binary repo and source repo.


Slackware is meant to be installed as a whole.
What if you want the simplicity of Slackware and the ability to
install a small base along with with a few other packages and optimize
it with reduced dependencies for new packages. This is a lot to ask,
other distro offer some of these options but gives you too much
overhead and headache.

The answer might lie in using something else, I am unable to put it in words,..
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[B Watson]

On 2/18/18, Jheengut Pritvi  wrote:
> But pkgsrc does not use the slackbuilds.org Slackbuilds to build packages.

Have you looked at sbotools? It's at least somewhat similar to
ports/pkgsrc (or anyway it's been described to me that way, I haven't
actually used it).

One problem with using actual NetBSD pkgsrc on Slackware is that it
has its own package database. It doesn't know about the Slack package
db in /var/log/packages, and when you use pkgsrc to install something,
no record of it gets created in /var/log/packages.

If you google for Slackware + pkgsrc, you probably will find an ancient
set of directions that you should *not* follow (it involves replacing
most of the OS with pkgsrc equivalents, and "rm -rf /var/log/packages"
is one of the steps in the procedure...)
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Jheengut Pritvi]

But pkgsrc does not use the slackbuilds.org Slackbuilds to build packages.

On 16 February 2018 at 14:11, Noryungi  wrote:
> If you go that way, may I draw your attention to the fact that NetBSD pkgsrc
> exists and works very well under Slackware?
>
> Why reinvent the wheel?
>
> On Feb 16, 2018 09:29, "Jheengut Pritvi"  wrote:
>>
>> With the forthcoming of Slackware 15.0, I have been nostalgic of the
>> days when I tried crazy thing with my Slackbox. One of those was using
>> BSD's ports and portage within Slackware. It was a succees and a
>> failure too. In those times, I was not using slackbuilds.org.
>> The big question:::
>> Is it worthwhile for a ports/portage/pacman like package manager for
>> Slackware that manages both binary and source packages?
>>
>>
>> It could be tool on top of pkgtool and sbopkg.
>>
>> What is your opinion?
>> ___
>> SlackBuilds-users mailing list
>> SlackBuilds-users@slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

Re: [Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Noryungi]

If you go that way, may I draw your attention to the fact that NetBSD
pkgsrc exists and works very well under Slackware?

Why reinvent the wheel?

On Feb 16, 2018 09:29, "Jheengut Pritvi"  wrote:

> With the forthcoming of Slackware 15.0, I have been nostalgic of the
> days when I tried crazy thing with my Slackbox. One of those was using
> BSD's ports and portage within Slackware. It was a succees and a
> failure too. In those times, I was not using slackbuilds.org.
> The big question:::
> Is it worthwhile for a ports/portage/pacman like package manager for
> Slackware that manages both binary and source packages?
>
>
> It could be tool on top of pkgtool and sbopkg.
>
> What is your opinion?
> ___
> SlackBuilds-users mailing list
> SlackBuilds-users@slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/

[Slackbuilds-users] Is it worthwhile for a ports like package manager for Slackware

[Jheengut Pritvi]

With the forthcoming of Slackware 15.0, I have been nostalgic of the
days when I tried crazy thing with my Slackbox. One of those was using
BSD's ports and portage within Slackware. It was a succees and a
failure too. In those times, I was not using slackbuilds.org.
The big question:::
Is it worthwhile for a ports/portage/pacman like package manager for
Slackware that manages both binary and source packages?


It could be tool on top of pkgtool and sbopkg.

What is your opinion?
___
SlackBuilds-users mailing list
SlackBuilds-users@slackbuilds.org
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/