From klaatu at mixedsignals.ml  Tue Jan  4 21:10:03 2022
From: klaatu at mixedsignals.ml (Klaatu)
Date: Wed, 05 Jan 2022 10:10:03 +1300
Subject: [Slackbuilds-users] What if we `source`d the version number
Message-ID: <4575009.ea4tHpRPHW@beast>

Why do we define the VERSION for a package in two separate files?

What if we replaced this line in foo.SlackBuild:
VERSION={VERSION:-0.0.1}

with this instead:
. ./$PRGNAM.info

The VERSION variable would get imported from a consolidated location (the 
.info file).

It seems to make more sense to me, and it makes trivial upgrades (the ones 
where I go in and just bump a version number to something I want to build) a 
one-file task.

Thoughts?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220105/c47a8857/attachment.htm>

From belka at caraus.de  Tue Jan  4 21:40:33 2022
From: belka at caraus.de (Eugen Wissner)
Date: Tue, 4 Jan 2022 22:40:33 +0100
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <4575009.ea4tHpRPHW@beast>
References: <4575009.ea4tHpRPHW@beast>
Message-ID: <20220104214033.ti35zkmdcnt5xxb7@desktop.caraus.net>

Yeah, would be nice. Slackware?s Slackbuilds try to determine the
version automatically based on the tarball in the directory, which
doesn't always work if I have multiple tarballs in the directory. And
the SBo SlackBuilds have the same information in two places; don't
repeat yourself.

On Wed, Jan 05, 2022 at 10:10:03AM +1300, Klaatu wrote:
> Why do we define the VERSION for a package in two separate files?
> 
> What if we replaced this line in foo.SlackBuild:
> VERSION={VERSION:-0.0.1}
> 
> with this instead:
> . ./$PRGNAM.info
> 
> The VERSION variable would get imported from a consolidated location (the 
> .info file).
> 
> It seems to make more sense to me, and it makes trivial upgrades (the ones 
> where I go in and just bump a version number to something I want to build) a 
> one-file task.
> 
> Thoughts?

> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 


From yalhcru at gmail.com  Tue Jan  4 21:39:07 2022
From: yalhcru at gmail.com (B Watson)
Date: Tue, 4 Jan 2022 16:39:07 -0500
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <4575009.ea4tHpRPHW@beast>
References: <4575009.ea4tHpRPHW@beast>
Message-ID: <CAN1hMuBxQ3y7GfZmxsp2=6j2Yyk-JVn6H1QjrvZsWrrS40fbmw@mail.gmail.com>

On 1/4/22, Klaatu <klaatu at mixedsignals.ml> wrote:
> Why do we define the VERSION for a package in two separate files?
>
> What if we replaced this line in foo.SlackBuild:
> VERSION={VERSION:-0.0.1}
>
> with this instead:
> . ./$PRGNAM.info

It'd take away the ability to override VERSION in the environment. A lot
of us do this:

  VERSION=1.2.3 sh foo.SlackBuild

...to attempt to build a new version of 'foo' with the existing
script. Of course this doesn't always work, but it works often enough
to be useful.

With your change, any user trying to use the script to build a newer
version would have to edit the .info file. Which is fine, but would
require changes in every automated tool that handles SBo builds (at
minimum, sbopkg and sbotools).

You could also change the .info file format, so instead of saying:

  VERSION="0.0.1"

it would say:

  VERSION="${VERSION:-0.0.1}"

This would allow your idea (sourcing the .info file) and the existing
practice (override VERSION in the environment) to coexist. But it would
likely break sbopkg and sbotools even worse.

From andrzej at telszewski.com  Tue Jan  4 21:48:46 2022
From: andrzej at telszewski.com (Andrzej Telszewski)
Date: Tue, 4 Jan 2022 21:48:46 +0000 (UTC)
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <4575009.ea4tHpRPHW@beast>
References: <4575009.ea4tHpRPHW@beast>
Message-ID: <89ad73bc-f907-4211-bd7b-57444cda1f05@telszewski.com>


Jan 4, 2022 10:11:00 PM Klaatu <klaatu at mixedsignals.ml>:

> Why do we define the VERSION for a package in two separate files?
> ?
> What if we replaced this line in foo.SlackBuild:
> VERSION={VERSION:-0.0.1}
> ?
> with this instead:
> . ./$PRGNAM.info
> ?
> The VERSION variable would get imported from a consolidated location (the .info file).
> ?
> It seems to make more sense to me, and it makes trivial upgrades (the ones where I go in and just bump a version number to something I want to build) a one-file task.
> ?
> Thoughts?

You can source .info before executing .SlackBuild to get the same effect. No changes needed. :-)

> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/


From dpross1100 at msn.com  Wed Jan  5 04:31:35 2022
From: dpross1100 at msn.com (Daniel Prosser)
Date: Tue, 04 Jan 2022 23:31:35 -0500
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <89ad73bc-f907-4211-bd7b-57444cda1f05@telszewski.com>
Message-ID: <SN6PR03MB3536B25D8B2E5F12F13234D5CC4B9@SN6PR03MB3536.namprd03.prod.outlook.com>

An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220104/f6ea7aa0/attachment.htm>

From lists at osh.id.au  Wed Jan  5 04:37:07 2022
From: lists at osh.id.au (David O'Shaughnessy)
Date: Wed, 05 Jan 2022 12:37:07 +0800
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <CAN1hMuBxQ3y7GfZmxsp2=6j2Yyk-JVn6H1QjrvZsWrrS40fbmw@mail.gmail.com>
References: <4575009.ea4tHpRPHW@beast>
 <CAN1hMuBxQ3y7GfZmxsp2=6j2Yyk-JVn6H1QjrvZsWrrS40fbmw@mail.gmail.com>
Message-ID: <32339548-24a5-436e-8eb5-082bab1c14ae@www.fastmail.com>

On Wed, 5 Jan 2022, at 5:39 AM, B Watson wrote:
> It'd take away the ability to override VERSION in the environment. A lot
> of us do this:
>
>   VERSION=1.2.3 sh foo.SlackBuild
>
> ...to attempt to build a new version of 'foo' with the existing
> script. Of course this doesn't always work, but it works often enough
> to be useful.

What about wrapping the original suggestion inside some simple logic, so that sourcing .info is only triggered if VERSION in the environment is empty?

--
Dave

From klaatu at mixedsignals.ml  Wed Jan  5 05:11:04 2022
From: klaatu at mixedsignals.ml (Klaatu)
Date: Wed, 05 Jan 2022 18:11:04 +1300
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <SN6PR03MB3536B25D8B2E5F12F13234D5CC4B9@SN6PR03MB3536.namprd03.prod.outlook.com>
References: <SN6PR03MB3536B25D8B2E5F12F13234D5CC4B9@SN6PR03MB3536.namprd03.prod.outlook.com>
Message-ID: <26914271.4eenUQpha9@beast>

On Wednesday, January 5, 2022 5:31:35 PM NZDT Daniel Prosser wrote:
> I believe the suggestion was to make life easier for package maintainers,
> not builders. 
> 

Both, actually.  The idea came to me because I was updating an application  
that was versioned 1.8 on SBo, but I found version 1.9 on Github. So I edited 
the .info file so that my build script would download 1.9, and then I commenced 
the build. Because I'd forgotten to update the .SlackBuild file, though, the 
build failed.

A quick fix, admittedly, but it occurred to me that it seemed non-optimized to 
have the same value in two places. Why not have it in one place instead? That 
way the human only has to interact with one file, instead of two, and anyway it 
"feels" like it's better design to have the value once, not twice.

-klaatu



> On Jan 4, 2022 4:48 PM, Andrzej Telszewski <andrzej at telszewski.com> wrote:
> 
> Jan 4, 2022 10:11:00 PM Klaatu <klaatu at mixedsignals.ml>:
> > Why do we define the VERSION for a package in two separate files?
> >  
> > What if we replaced this line in foo.SlackBuild:
> > VERSION={VERSION:-0.0.1}
> >  
> > with this instead:
> > . ./$PRGNAM.info
> >  
> > The VERSION variable would get imported from a consolidated location (the
> > .info file). 
> > It seems to make more sense to me, and it makes trivial upgrades (the ones
> > where I go in and just bump a version number to something I want to
> > build) a one-file task. 
> > Thoughts?
> 
> You can source .info before executing .SlackBuild to get the same effect. No
> changes needed. :-)
> > _______________________________________________
> > SlackBuilds-users mailing list
> > SlackBuilds-users at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/



From didier at slint.fr  Fri Jan  7 18:54:16 2022
From: didier at slint.fr (Didier Spaier)
Date: Fri, 7 Jan 2022 19:54:16 +0100
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
Message-ID: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>

Hello,

I don't have the time to properly maintain them, in addition to Slint maintenance.

List:
abcde
bdf2psf
bicon
cd-discid
doclifter
espeakup
gksu
libdca
libgksu
libgtop
libshout
mkcue
perl-Encode-EUCJPASCII
perl-Encode-HanExtra
perl-Encode-ISO2022
perl-Encode-JISX0213
perl-MIME-Charset
perl-MusicBrainz-DiscID
perl-Text-CharWidth
perl-Text-WrapI18N
perl-Unicode-LineBreak
perl-WebService-MusicBrainz
po4a
qControlCenter
txt2tags

I am ready to help help anyone wanting to take them over.

I generally ship packages in Slint build from them, possibly with modifications.

The source repository of these packages is:
https://slackware.uk/slint/x86_64/slint-14.2.1/source/

I wish a Happy New Year to all of you.

Cheers,
Didier

From slackbuilds at schoepfer.info  Sat Jan  8 06:20:12 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sat, 08 Jan 2022 07:20:12 +0100
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
In-Reply-To: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
References: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
Message-ID: <f451f9b69e10c3207d9d1748b7fb6be1@schoepfer.info>

Hi,

> I don't have the time to properly maintain them, in addition to Slint
> maintenance.

i'll take

> abcde
> cd-discid

but not
> perl-MusicBrainz-DiscID
> perl-WebService-MusicBrainz

as these are no hard dependencies of abcde, which i'll then note as 
optional packages in abcde.


Sidenote,
> libgtop
is part of -current and should be dropped from SBo


Johannes

From yalhcru at gmail.com  Sat Jan  8 17:09:09 2022
From: yalhcru at gmail.com (B Watson)
Date: Sat, 8 Jan 2022 12:09:09 -0500
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
In-Reply-To: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
References: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
Message-ID: <CAN1hMuC_MJgRjbW8Nc-SsF9ebRsxHy5ERC6S9xZpJxg7SySGbQ@mail.gmail.com>

On 1/7/22, Didier Spaier <didier at slint.fr> wrote:
> Hello,
>
> I don't have the time to properly maintain them, in addition to Slint
> maintenance.

That's a bummer, we're going to miss you. Hopefully you'll still be
around on the mailing list and maybe IRC.

> bdf2psf

I'll take this one, it's an optional dep for one of mine.

> bicon
> doclifter
> txt2tags
> po4a

I'll take these, they look interesting and/or useful.

> perl-Encode-EUCJPASCII
> perl-Encode-HanExtra
> perl-Encode-ISO2022
> perl-Encode-JISX0213
> perl-MIME-Charset
> perl-MusicBrainz-DiscID
> perl-Text-CharWidth
> perl-Text-WrapI18N
> perl-Unicode-LineBreak
> perl-WebService-MusicBrainz

And these. A few of them are optional or required for some of mine.

From yalhcru at gmail.com  Sat Jan  8 17:10:33 2022
From: yalhcru at gmail.com (B Watson)
Date: Sat, 8 Jan 2022 12:10:33 -0500
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
In-Reply-To: <f451f9b69e10c3207d9d1748b7fb6be1@schoepfer.info>
References: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
 <f451f9b69e10c3207d9d1748b7fb6be1@schoepfer.info>
Message-ID: <CAN1hMuDE+A8sU5kx3O3Lt-969OqRj3uex79+2Gn0ANg_5vL1iQ@mail.gmail.com>

On 1/8/22, Franzen via SlackBuilds-users
<slackbuilds-users at slackbuilds.org> wrote:
>
> i'll take
>
>> abcde
>> cd-discid

What about mkcue? It's an optional dep for abcde, and it has no
external deps itself.

From slackbuilds at schoepfer.info  Sun Jan  9 09:50:25 2022
From: slackbuilds at schoepfer.info (Franzen)
Date: Sun, 09 Jan 2022 10:50:25 +0100
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
In-Reply-To: <CAN1hMuDE+A8sU5kx3O3Lt-969OqRj3uex79+2Gn0ANg_5vL1iQ@mail.gmail.com>
References: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
 <f451f9b69e10c3207d9d1748b7fb6be1@schoepfer.info>
 <CAN1hMuDE+A8sU5kx3O3Lt-969OqRj3uex79+2Gn0ANg_5vL1iQ@mail.gmail.com>
Message-ID: <1cfbe921780868d3021e5233c0916278@schoepfer.info>

>> i'll take
>> 
>>> abcde
>>> cd-discid
> 
> What about mkcue? It's an optional dep for abcde, and it has no
> external deps itself.

Ok, i'll take that too.

Johannes

From yalhcru at gmail.com  Mon Jan 10 17:07:37 2022
From: yalhcru at gmail.com (B Watson)
Date: Mon, 10 Jan 2022 12:07:37 -0500
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
In-Reply-To: <CAN1hMuC_MJgRjbW8Nc-SsF9ebRsxHy5ERC6S9xZpJxg7SySGbQ@mail.gmail.com>
References: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
 <CAN1hMuC_MJgRjbW8Nc-SsF9ebRsxHy5ERC6S9xZpJxg7SySGbQ@mail.gmail.com>
Message-ID: <CAN1hMuBogWoS45jSbAZ7Xs5f9n3p9aeeMUfh0iQdyaWMSkF0Xg@mail.gmail.com>

Didier, do you mind if I relicense the builds I'm taking over from
you? I prefer the WTFPL for SlackBuilds.

From pbraun at nethence.com  Mon Jan 10 17:34:20 2022
From: pbraun at nethence.com (Pierre-Philipp Braun)
Date: Mon, 10 Jan 2022 20:34:20 +0300
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <26914271.4eenUQpha9@beast>
References: <SN6PR03MB3536B25D8B2E5F12F13234D5CC4B9@SN6PR03MB3536.namprd03.prod.outlook.com>
 <26914271.4eenUQpha9@beast>
Message-ID: <8e3f53ae-b29d-6e1c-9185-e510b3aaa1fd@nethence.com>

On 05/01/2022 08:11, Klaatu wrote:
> A quick fix, admittedly, but it occurred to me that it seemed non-optimized to
> have the same value in two places. Why not have it in one place instead? That
> way the human only has to interact with one file, instead of two, and anyway it
> "feels" like it's better design to have the value once, not twice.

Hello

that's a cool thread and I agree that duplicate information is painful 
to manage.  Here's a draft that would make both happy, maintainers and 
builders (KSH style, sorry, but easy enough to adapt):

foo.SlackBuild

[[ -z $VERSION ]] && . ./foo.info

That way, you can continue enforce VERSION from the command prompt when 
ever needed.

Cheers
-- 
Pierre-Philipp Braun
SMTP Health Campaign: enforce STARTTLS and verify MX certificates
<https://nethence.com/smtp/>

From didier at slint.fr  Mon Jan 10 17:52:22 2022
From: didier at slint.fr (Didier Spaier)
Date: Mon, 10 Jan 2022 18:52:22 +0100
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
In-Reply-To: <CAN1hMuBogWoS45jSbAZ7Xs5f9n3p9aeeMUfh0iQdyaWMSkF0Xg@mail.gmail.com>
References: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
 <CAN1hMuC_MJgRjbW8Nc-SsF9ebRsxHy5ERC6S9xZpJxg7SySGbQ@mail.gmail.com>
 <CAN1hMuBogWoS45jSbAZ7Xs5f9n3p9aeeMUfh0iQdyaWMSkF0Xg@mail.gmail.com>
Message-ID: <a89e7702-3c2f-3b0d-bdea-0ed64500dd37@slint.fr>

Hi,

that's fine with me. I now tend to go public domain cf. https://unlicense.org/,
but as stated in https://slackbuilds.org/guidelines/ this is not allowed for
SBo. However Slackware ships SQLite which is in the Public Domain
https://www.sqlite.org/copyright.html ;)

Oh, and Martin Quinson has released po4a-0.66. It builds and run with no issue
here. Example of usage:
https://github.com/DidierSpaier/translations/tree/master/HandBook, the one
liners there are just po4a commands.

> Hopefully you'll still be around on the mailing list and maybe IRC.

I will certainly stay on the mailing list, on IRC once in a while.

Cheers,
Didier

Le 10/01/2022 ? 18:07, B Watson a ?crit?:
> Didier, do you mind if I relicense the builds I'm taking over from
> you? I prefer the WTFPL for SlackBuilds.

From kjhambrick at gmail.com  Mon Jan 10 22:17:04 2022
From: kjhambrick at gmail.com (Konrad J Hambrick)
Date: Mon, 10 Jan 2022 16:17:04 -0600
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <4575009.ea4tHpRPHW@beast>
References: <4575009.ea4tHpRPHW@beast>
Message-ID: <CANBHt+MkJLdqUha3WYNDYRx1uRjCV_=d0tJKaFEXJDCNrObBeg@mail.gmail.com>

Klaatu --

That's pretty much what I do ( source $PROGRAM.info ) in my
do-SlackBuild.$PRGNAM scripts.

But I do that in a wrapper-script that invokes the standard SlackBuild.

The Code below is auto-generated by a get-SB-pkg script ( example:
get-SB-pkg intel-microcode )

As you can see, the $PRGNAM.info File is sourced by the wrapper script but I
can still override the VERSION as expected:

   VERSION=1.2.3.4 ./do-SlackBuild.intel-microcode

One can also set TAG= to append a TAG ( like say, TAG=_kjh )

As a bonus, the do-wrapper logs all the output to
$PRGNAM-SlackBuild-$VERSION$TAG.log

Anyhow ... my $0.02 ... no need to change the SlackBuilds ( PLEASE don't
change the SlackBuilds :)

-- kjh

#!/bin/sh
>
> DoName="intel-microcode.SlackBuild"
>
> MyVersion="$VERSION"
>
> . ./intel-microcode.info
>
> [ "$MyVersion" = "" ] && MyVersion="$VERSION"
>
> LogNam="$DoName-$MyVersion$TAG.log"
>
> unset PRGNAM
> unset VERSION
> unset HOMEPAGE
> unset DOWNLOAD
> unset MD5SUM
> unset DOWNLOAD_x86_64
> unset MD5SUM_x86_64
> unset REQUIRES
> unset MAINTAINER
> unset EMAIL
> #
> # set and export any extra variables here
> #
> export TAG
> export VERSION="$MyVersion"
>


> # do the deed
> #
> echo "$DoName startup  at `date`"  |tee    $LogNam
> ./$DoName 2>&1                     |tee -a $LogNam
> #
> RetCode=${PIPESTATUS[0]}
> #
> [ "$RetCode" = "0" ] && RetStr="complete" || RetStr="FAILED  "
> #
> # optional pre-installation instructions  here
> #
> #
> # optional pre-installation instructions there
> #
> # log your results
> #
> echo "$DoName $RetStr at `date` ... RetCode = $RetCode" |tee -a $LogNam
> exit $RetCode
>


On Tue, Jan 4, 2022 at 3:11 PM Klaatu <klaatu at mixedsignals.ml> wrote:

> Why do we define the VERSION for a package in two separate files?
>
>
>
> What if we replaced this line in foo.SlackBuild:
>
> VERSION={VERSION:-0.0.1}
>
>
>
> with this instead:
>
> . ./$PRGNAM.info
>
>
>
> The VERSION variable would get imported from a consolidated location (the
> .info file).
>
>
>
> It seems to make more sense to me, and it makes trivial upgrades (the ones
> where I go in and just bump a version number to something I want to build)
> a one-file task.
>
>
>
> Thoughts?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220110/fac514fc/attachment.htm>

From rcb at beco.cc  Tue Jan 11 02:18:22 2022
From: rcb at beco.cc (Beco)
Date: Mon, 10 Jan 2022 23:18:22 -0300
Subject: [Slackbuilds-users] Howto for slackware tgz
Message-ID: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>

Hello there, Slack users,

I just joined.
I hope you are all doing well, and that this list is still active.

I am migrating from Debian systemD. I tried Devuan as well. It is
difficult to change distros when you have many computers/notebooks and
you want them to share the same distro.

Some of my small scripts and programs need to adapt. It is not a big
deal, but I want them to keep organized. I think the best way is to
reorganize them within the parameters and directory structure of a
slackware package.


Please, what is a good updated detailed source of explanation about
the format and internals of a tgz tar-ball (package)?


Thanks and still in time, happy 2022.

-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not
sure you realize that what you heard is not what I meant" -- Alan
Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Essa mensagem ? destinada exclusivamente ao seu destinat?rio e pode
conter informa??es confidenciais, protegidas por sigilo profissional,
direitos autorais reservados, ou cuja divulga??o seja proibida por
lei. O uso n?o autorizado de tais informa??es ? proibido e est?
sujeito ?s penalidades cab?veis.

This message is intended exclusively for its addressee and may contain
information that is confidential and protected by a professional
privilege, reserved copyright, or whose disclosure is prohibited by
law. Unauthorised use of such information is prohibited and subject to
applicable penalties.

From jebrhansen+SBo at gmail.com  Tue Jan 11 03:29:05 2022
From: jebrhansen+SBo at gmail.com (Jeremy Hansen)
Date: Mon, 10 Jan 2022 20:29:05 -0700
Subject: [Slackbuilds-users] Howto for slackware tgz
In-Reply-To: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>
References: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>
Message-ID: <CANi9qSvX8Z1VDVuBuiL7DNTa66x=o_8LoEgszfWu8AtvPZVK6w@mail.gmail.com>

On Mon, Jan 10, 2022, 7:19 PM Beco via SlackBuilds-users <
slackbuilds-users at slackbuilds.org> wrote:

> Hello there, Slack users,
>
> I just joined.
> I hope you are all doing well, and that this list is still active.
>
> I am migrating from Debian systemD. I tried Devuan as well. It is
> difficult to change distros when you have many computers/notebooks and
> you want them to share the same distro.
>
> Some of my small scripts and programs need to adapt. It is not a big
> deal, but I want them to keep organized. I think the best way is to
> reorganize them within the parameters and directory structure of a
> slackware package.
>
>
> Please, what is a good updated detailed source of explanation about
> the format and internals of a tgz tar-ball (package)?
>
>
> Thanks and still in time, happy 2022.
>


Welcome! They're pretty simple. The majority of it is simply extracted to
the root filesystem and is stored with the exact layout it is expected to
have on the root filesystem.

Where it differs is the install/ directory. This houses the files for the
Slackware package manager. The two most common are slack-desc and
doinst.sh. The former is used as the information displayed by Slackware's
package manager during installation and maintenance. The latter is an
optional file that is run immediately after the package is installed. You
can see SBo's templates for both at the below address.

Good luck,
Jeremy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220110/ab6abf19/attachment.htm>

From slackalaxy at gmail.com  Tue Jan 11 08:44:47 2022
From: slackalaxy at gmail.com (Petar Petrov)
Date: Tue, 11 Jan 2022 10:44:47 +0200
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <CANBHt+MkJLdqUha3WYNDYRx1uRjCV_=d0tJKaFEXJDCNrObBeg@mail.gmail.com>
References: <4575009.ea4tHpRPHW@beast>
 <CANBHt+MkJLdqUha3WYNDYRx1uRjCV_=d0tJKaFEXJDCNrObBeg@mail.gmail.com>
Message-ID: <CAKXpWBfAktQNbY7jncPGK2My+aqNw3zySRDmxbWifoiROynhOg@mail.gmail.com>

Hi guys,

if you aim to simplify things, you can take it even further...

Why do you need $PRGNAM.SlackBuild, $PRGNAM.info, etc...? Anyway, all
of these are in a folder called $PRGNAM, right? Why should the script
have a unique name, instead of just SlackBuild (like the PKGBUILD
files in Arch)?

i know it's not going to happen, since this is not how Slackware does things.

-petar

On Tue, 11 Jan 2022 at 00:16, Konrad J Hambrick <kjhambrick at gmail.com> wrote:
>
> Klaatu --
>
> That's pretty much what I do ( source $PROGRAM.info ) in my do-SlackBuild.$PRGNAM scripts.
>
> But I do that in a wrapper-script that invokes the standard SlackBuild.
>
> The Code below is auto-generated by a get-SB-pkg script ( example:  get-SB-pkg intel-microcode )
>
> As you can see, the $PRGNAM.info File is sourced by the wrapper script but I can still override the VERSION as expected:
>
>    VERSION=1.2.3.4 ./do-SlackBuild.intel-microcode
>
> One can also set TAG= to append a TAG ( like say, TAG=_kjh )
>
> As a bonus, the do-wrapper logs all the output to $PRGNAM-SlackBuild-$VERSION$TAG.log
>
> Anyhow ... my $0.02 ... no need to change the SlackBuilds ( PLEASE don't change the SlackBuilds :)
>
> -- kjh
>
>> #!/bin/sh
>>
>> DoName="intel-microcode.SlackBuild"
>>
>> MyVersion="$VERSION"
>>
>> . ./intel-microcode.info
>>
>> [ "$MyVersion" = "" ] && MyVersion="$VERSION"
>>
>> LogNam="$DoName-$MyVersion$TAG.log"
>>
>> unset PRGNAM
>> unset VERSION
>> unset HOMEPAGE
>> unset DOWNLOAD
>> unset MD5SUM
>> unset DOWNLOAD_x86_64
>> unset MD5SUM_x86_64
>> unset REQUIRES
>> unset MAINTAINER
>> unset EMAIL
>> #
>> # set and export any extra variables here
>> #
>> export TAG
>> export VERSION="$MyVersion"
>
>
>>
>> # do the deed
>> #
>> echo "$DoName startup  at `date`"  |tee    $LogNam
>> ./$DoName 2>&1                     |tee -a $LogNam
>> #
>> RetCode=${PIPESTATUS[0]}
>> #
>> [ "$RetCode" = "0" ] && RetStr="complete" || RetStr="FAILED  "
>> #
>> # optional pre-installation instructions  here
>> #
>> #
>> # optional pre-installation instructions there
>> #
>> # log your results
>> #
>> echo "$DoName $RetStr at `date` ... RetCode = $RetCode" |tee -a $LogNam
>> exit $RetCode
>
>
>
> On Tue, Jan 4, 2022 at 3:11 PM Klaatu <klaatu at mixedsignals.ml> wrote:
>>
>> Why do we define the VERSION for a package in two separate files?
>>
>>
>>
>> What if we replaced this line in foo.SlackBuild:
>>
>> VERSION={VERSION:-0.0.1}
>>
>>
>>
>> with this instead:
>>
>> . ./$PRGNAM.info
>>
>>
>>
>> The VERSION variable would get imported from a consolidated location (the .info file).
>>
>>
>>
>> It seems to make more sense to me, and it makes trivial upgrades (the ones where I go in and just bump a version number to something I want to build) a one-file task.
>>
>>
>>
>> Thoughts?
>>
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>

From belka at caraus.de  Tue Jan 11 09:03:40 2022
From: belka at caraus.de (Eugen Wissner)
Date: Tue, 11 Jan 2022 10:03:40 +0100
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <CAKXpWBfAktQNbY7jncPGK2My+aqNw3zySRDmxbWifoiROynhOg@mail.gmail.com>
References: <4575009.ea4tHpRPHW@beast>
 <CANBHt+MkJLdqUha3WYNDYRx1uRjCV_=d0tJKaFEXJDCNrObBeg@mail.gmail.com>
 <CAKXpWBfAktQNbY7jncPGK2My+aqNw3zySRDmxbWifoiROynhOg@mail.gmail.com>
Message-ID: <20220111090340.fsbul6qsdqu5oqbx@desktop.caraus.net>

I don't update the package name each time, but I often update the
package version.

On Tue, Jan 11, 2022 at 10:44:47AM +0200, Petar Petrov wrote:
> Hi guys,
> 
> if you aim to simplify things, you can take it even further...
> 
> Why do you need $PRGNAM.SlackBuild, $PRGNAM.info, etc...? Anyway, all
> of these are in a folder called $PRGNAM, right? Why should the script
> have a unique name, instead of just SlackBuild (like the PKGBUILD
> files in Arch)?
> 
> i know it's not going to happen, since this is not how Slackware does things.
> 
> -petar
> 
> On Tue, 11 Jan 2022 at 00:16, Konrad J Hambrick <kjhambrick at gmail.com> wrote:
> >
> > Klaatu --
> >
> > That's pretty much what I do ( source $PROGRAM.info ) in my do-SlackBuild.$PRGNAM scripts.
> >
> > But I do that in a wrapper-script that invokes the standard SlackBuild.
> >
> > The Code below is auto-generated by a get-SB-pkg script ( example:  get-SB-pkg intel-microcode )
> >
> > As you can see, the $PRGNAM.info File is sourced by the wrapper script but I can still override the VERSION as expected:
> >
> >    VERSION=1.2.3.4 ./do-SlackBuild.intel-microcode
> >
> > One can also set TAG= to append a TAG ( like say, TAG=_kjh )
> >
> > As a bonus, the do-wrapper logs all the output to $PRGNAM-SlackBuild-$VERSION$TAG.log
> >
> > Anyhow ... my $0.02 ... no need to change the SlackBuilds ( PLEASE don't change the SlackBuilds :)
> >
> > -- kjh
> >
> >> #!/bin/sh
> >>
> >> DoName="intel-microcode.SlackBuild"
> >>
> >> MyVersion="$VERSION"
> >>
> >> . ./intel-microcode.info
> >>
> >> [ "$MyVersion" = "" ] && MyVersion="$VERSION"
> >>
> >> LogNam="$DoName-$MyVersion$TAG.log"
> >>
> >> unset PRGNAM
> >> unset VERSION
> >> unset HOMEPAGE
> >> unset DOWNLOAD
> >> unset MD5SUM
> >> unset DOWNLOAD_x86_64
> >> unset MD5SUM_x86_64
> >> unset REQUIRES
> >> unset MAINTAINER
> >> unset EMAIL
> >> #
> >> # set and export any extra variables here
> >> #
> >> export TAG
> >> export VERSION="$MyVersion"
> >
> >
> >>
> >> # do the deed
> >> #
> >> echo "$DoName startup  at `date`"  |tee    $LogNam
> >> ./$DoName 2>&1                     |tee -a $LogNam
> >> #
> >> RetCode=${PIPESTATUS[0]}
> >> #
> >> [ "$RetCode" = "0" ] && RetStr="complete" || RetStr="FAILED  "
> >> #
> >> # optional pre-installation instructions  here
> >> #
> >> #
> >> # optional pre-installation instructions there
> >> #
> >> # log your results
> >> #
> >> echo "$DoName $RetStr at `date` ... RetCode = $RetCode" |tee -a $LogNam
> >> exit $RetCode
> >
> >
> >
> > On Tue, Jan 4, 2022 at 3:11 PM Klaatu <klaatu at mixedsignals.ml> wrote:
> >>
> >> Why do we define the VERSION for a package in two separate files?
> >>
> >>
> >>
> >> What if we replaced this line in foo.SlackBuild:
> >>
> >> VERSION={VERSION:-0.0.1}
> >>
> >>
> >>
> >> with this instead:
> >>
> >> . ./$PRGNAM.info
> >>
> >>
> >>
> >> The VERSION variable would get imported from a consolidated location (the .info file).
> >>
> >>
> >>
> >> It seems to make more sense to me, and it makes trivial upgrades (the ones where I go in and just bump a version number to something I want to build) a one-file task.
> >>
> >>
> >>
> >> Thoughts?
> >>
> >> _______________________________________________
> >> SlackBuilds-users mailing list
> >> SlackBuilds-users at 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 at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
> 

From kristofru at gmail.com  Wed Jan 12 13:42:26 2022
From: kristofru at gmail.com (Chris Abela)
Date: Wed, 12 Jan 2022 14:42:26 +0100
Subject: [Slackbuilds-users] Howto for slackware tgz
In-Reply-To: <CANi9qSvX8Z1VDVuBuiL7DNTa66x=o_8LoEgszfWu8AtvPZVK6w@mail.gmail.com>
References: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>
 <CANi9qSvX8Z1VDVuBuiL7DNTa66x=o_8LoEgszfWu8AtvPZVK6w@mail.gmail.com>
Message-ID: <CAJ2_kYrLFsjK8i5YTioqnFxVFCWojW6c+V3Mzar1E9OD5aguMA@mail.gmail.com>

See here:

https://www.slackwiki.com/Packages
https://www.slackwiki.com/Building_A_Package
http://docs.slackware.com/howtos:slackware_admin:building_packages_with_sbopkg
http://docs.slackware.com/howtos:find_packages_with_filenames
http://docs.slackware.com/howtos:slackware_admin:querying_installed_packages

You will find that as Slackware does not track dependencies, it is
resilient to most hacking possibilities.

As a tutorial, try to build a helloworld package.

On Tue, Jan 11, 2022 at 4:29 AM Jeremy Hansen <jebrhansen+SBo at gmail.com>
wrote:

>
>
> On Mon, Jan 10, 2022, 7:19 PM Beco via SlackBuilds-users <
> slackbuilds-users at slackbuilds.org> wrote:
>
>> Hello there, Slack users,
>>
>> I just joined.
>> I hope you are all doing well, and that this list is still active.
>>
>> I am migrating from Debian systemD. I tried Devuan as well. It is
>> difficult to change distros when you have many computers/notebooks and
>> you want them to share the same distro.
>>
>> Some of my small scripts and programs need to adapt. It is not a big
>> deal, but I want them to keep organized. I think the best way is to
>> reorganize them within the parameters and directory structure of a
>> slackware package.
>>
>>
>> Please, what is a good updated detailed source of explanation about
>> the format and internals of a tgz tar-ball (package)?
>>
>>
>> Thanks and still in time, happy 2022.
>>
>
>
> Welcome! They're pretty simple. The majority of it is simply extracted to
> the root filesystem and is stored with the exact layout it is expected to
> have on the root filesystem.
>
> Where it differs is the install/ directory. This houses the files for the
> Slackware package manager. The two most common are slack-desc and
> doinst.sh. The former is used as the information displayed by Slackware's
> package manager during installation and maintenance. The latter is an
> optional file that is run immediately after the package is installed. You
> can see SBo's templates for both at the below address.
>
> Good luck,
> Jeremy
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220112/e483e360/attachment.htm>

From rcb at beco.cc  Thu Jan 13 01:39:44 2022
From: rcb at beco.cc (Beco)
Date: Wed, 12 Jan 2022 22:39:44 -0300
Subject: [Slackbuilds-users] Howto for slackware tgz
In-Reply-To: <CAJ2_kYrLFsjK8i5YTioqnFxVFCWojW6c+V3Mzar1E9OD5aguMA@mail.gmail.com>
References: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>
 <CANi9qSvX8Z1VDVuBuiL7DNTa66x=o_8LoEgszfWu8AtvPZVK6w@mail.gmail.com>
 <CAJ2_kYrLFsjK8i5YTioqnFxVFCWojW6c+V3Mzar1E9OD5aguMA@mail.gmail.com>
Message-ID: <CALuYw2yuoOHf8xE-M52ngincDp3sqjRm_Q+GMf8RsTPcHoSiqg@mail.gmail.com>

Hi Jeremy, hi Chris,

Thanks for the tips, guys.

I'll take a look at every link.

Currently I'm having trouble with my printer, Epson M105, and I'm
trying to adapt source code from drivers I've found in "src.rpm" to
slackware package format.

Maybe I should start with something simpler, even though I'm an
experienced linuxer from a long time, each distro has its own
challenges.

Best regards,
B?co


On Wed, 12 Jan 2022 at 10:42, Chris Abela <kristofru at gmail.com> wrote:
>
> See here:
>
> https://www.slackwiki.com/Packages
> https://www.slackwiki.com/Building_A_Package
> http://docs.slackware.com/howtos:slackware_admin:building_packages_with_sbopkg
> http://docs.slackware.com/howtos:find_packages_with_filenames
> http://docs.slackware.com/howtos:slackware_admin:querying_installed_packages
>
> You will find that as Slackware does not track dependencies, it is resilient to most hacking possibilities.
>
> As a tutorial, try to build a helloworld package.
>
> On Tue, Jan 11, 2022 at 4:29 AM Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:
>>
>>
>>
>> On Mon, Jan 10, 2022, 7:19 PM Beco via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:
>>>
>>> Hello there, Slack users,
>>>
>>> I just joined.
>>> I hope you are all doing well, and that this list is still active.
>>>
>>> I am migrating from Debian systemD. I tried Devuan as well. It is
>>> difficult to change distros when you have many computers/notebooks and
>>> you want them to share the same distro.
>>>
>>> Some of my small scripts and programs need to adapt. It is not a big
>>> deal, but I want them to keep organized. I think the best way is to
>>> reorganize them within the parameters and directory structure of a
>>> slackware package.
>>>
>>>
>>> Please, what is a good updated detailed source of explanation about
>>> the format and internals of a tgz tar-ball (package)?
>>>
>>>
>>> Thanks and still in time, happy 2022.
>>
>>
>>
>> Welcome! They're pretty simple. The majority of it is simply extracted to the root filesystem and is stored with the exact layout it is expected to have on the root filesystem.
>>
>> Where it differs is the install/ directory. This houses the files for the Slackware package manager. The two most common are slack-desc and doinst.sh. The former is used as the information displayed by Slackware's package manager during installation and maintenance. The latter is an optional file that is run immediately after the package is installed. You can see SBo's templates for both at the below address.
>>
>> Good luck,
>> Jeremy
>> _______________________________________________
>> SlackBuilds-users mailing list
>> SlackBuilds-users at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>


-- 
Dr Beco
A.I. researcher

"I know you think you understand what you thought I said but I'm not
sure you realize that what you heard is not what I meant" -- Alan
Greenspan

GPG Key: https://pgp.mit.edu/pks/lookup?op=vindex&search=0x5A107A425102382A
Creation date: pgp.mit.edu ID as of 2014-11-09

Essa mensagem ? destinada exclusivamente ao seu destinat?rio e pode
conter informa??es confidenciais, protegidas por sigilo profissional,
direitos autorais reservados, ou cuja divulga??o seja proibida por
lei. O uso n?o autorizado de tais informa??es ? proibido e est?
sujeito ?s penalidades cab?veis.

This message is intended exclusively for its addressee and may contain
information that is confidential and protected by a professional
privilege, reserved copyright, or whose disclosure is prohibited by
law. Unauthorised use of such information is prohibited and subject to
applicable penalties.

From chris.willing at linux.com  Thu Jan 13 02:38:11 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Thu, 13 Jan 2022 12:38:11 +1000
Subject: [Slackbuilds-users] Howto for slackware tgz
In-Reply-To: <CALuYw2yuoOHf8xE-M52ngincDp3sqjRm_Q+GMf8RsTPcHoSiqg@mail.gmail.com>
References: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>
 <CANi9qSvX8Z1VDVuBuiL7DNTa66x=o_8LoEgszfWu8AtvPZVK6w@mail.gmail.com>
 <CAJ2_kYrLFsjK8i5YTioqnFxVFCWojW6c+V3Mzar1E9OD5aguMA@mail.gmail.com>
 <CALuYw2yuoOHf8xE-M52ngincDp3sqjRm_Q+GMf8RsTPcHoSiqg@mail.gmail.com>
Message-ID: <e074c374-0aac-cda4-1e37-6b2662c28e76@linux.com>

On 13/1/22 11:39, Beco via SlackBuilds-users wrote:
> Hi Jeremy, hi Chris,
> 
> Thanks for the tips, guys.
> 
> I'll take a look at every link.
> 
> Currently I'm having trouble with my printer, Epson M105, and I'm
> trying to adapt source code from drivers I've found in "src.rpm" to
> slackware package format.
> 

Have a look at:
	https://slackbuilds.org/repository/14.2/system/epson-printer-utility/

whose README.models claims to support the M105 Series (and is based on
a src.rpm too).


chris


> Maybe I should start with something simpler, even though I'm an
> experienced linuxer from a long time, each distro has its own
> challenges.
> 
> Best regards,
> B?co
> 
> 
> On Wed, 12 Jan 2022 at 10:42, Chris Abela <kristofru at gmail.com> wrote:
>>
>> See here:
>>
>> https://www.slackwiki.com/Packages
>> https://www.slackwiki.com/Building_A_Package
>> http://docs.slackware.com/howtos:slackware_admin:building_packages_with_sbopkg
>> http://docs.slackware.com/howtos:find_packages_with_filenames
>> http://docs.slackware.com/howtos:slackware_admin:querying_installed_packages
>>
>> You will find that as Slackware does not track dependencies, it is resilient to most hacking possibilities.
>>
>> As a tutorial, try to build a helloworld package.
>>
>> On Tue, Jan 11, 2022 at 4:29 AM Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:
>>>
>>>
>>>
>>> On Mon, Jan 10, 2022, 7:19 PM Beco via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:
>>>>
>>>> Hello there, Slack users,
>>>>
>>>> I just joined.
>>>> I hope you are all doing well, and that this list is still active.
>>>>
>>>> I am migrating from Debian systemD. I tried Devuan as well. It is
>>>> difficult to change distros when you have many computers/notebooks and
>>>> you want them to share the same distro.
>>>>
>>>> Some of my small scripts and programs need to adapt. It is not a big
>>>> deal, but I want them to keep organized. I think the best way is to
>>>> reorganize them within the parameters and directory structure of a
>>>> slackware package.
>>>>
>>>>
>>>> Please, what is a good updated detailed source of explanation about
>>>> the format and internals of a tgz tar-ball (package)?
>>>>
>>>>
>>>> Thanks and still in time, happy 2022.
>>>
>>>
>>>
>>> Welcome! They're pretty simple. The majority of it is simply extracted to the root filesystem and is stored with the exact layout it is expected to have on the root filesystem.
>>>
>>> Where it differs is the install/ directory. This houses the files for the Slackware package manager. The two most common are slack-desc and doinst.sh. The former is used as the information displayed by Slackware's package manager during installation and maintenance. The latter is an optional file that is run immediately after the package is installed. You can see SBo's templates for both at the below address.
>>>
>>> Good luck,
>>> Jeremy
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at 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 at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
> 
> 


From slackbuilds at ninefamily.com  Thu Jan 13 03:02:19 2022
From: slackbuilds at ninefamily.com (slackbuilds at ninefamily.com)
Date: Wed, 12 Jan 2022 22:02:19 -0500
Subject: [Slackbuilds-users] Howto for slackware tgz
In-Reply-To: <47f3a7de-2a7a-65b5-e0d4-b5516d21557e@ninefamily.com>
References: <47f3a7de-2a7a-65b5-e0d4-b5516d21557e@ninefamily.com>
Message-ID: <74c7ff63-1c6b-26a7-9759-30902d038e36@ninefamily.com>


There is already an rpm2tgz within slackware

On 1/12/22 20:39, Beco via SlackBuilds-users wrote:
> Hi Jeremy, hi Chris,
>
> Thanks for the tips, guys.
>
> I'll take a look at every link.
>
> Currently I'm having trouble with my printer, Epson M105, and I'm
> trying to adapt source code from drivers I've found in "src.rpm" to
> slackware package format.
>
> Maybe I should start with something simpler, even though I'm an
> experienced linuxer from a long time, each distro has its own
> challenges.
>
> Best regards,
> B?co
>
>
> On Wed, 12 Jan 2022 at 10:42, Chris Abela <kristofru at gmail.com> wrote:
>> See here:
>>
>> https://www.slackwiki.com/Packages
>> https://www.slackwiki.com/Building_A_Package
>> http://docs.slackware.com/howtos:slackware_admin:building_packages_with_sbopkg
>> http://docs.slackware.com/howtos:find_packages_with_filenames
>> http://docs.slackware.com/howtos:slackware_admin:querying_installed_packages
>>
>> You will find that as Slackware does not track dependencies, it is resilient to most hacking possibilities.
>>
>> As a tutorial, try to build a helloworld package.
>>
>> On Tue, Jan 11, 2022 at 4:29 AM Jeremy Hansen <jebrhansen+SBo at gmail.com> wrote:
>>>
>>> On Mon, Jan 10, 2022, 7:19 PM Beco via SlackBuilds-users <slackbuilds-users at slackbuilds.org> wrote:
>>>> Hello there, Slack users,
>>>>
>>>> I just joined.
>>>> I hope you are all doing well, and that this list is still active.
>>>>
>>>> I am migrating from Debian systemD. I tried Devuan as well. It is
>>>> difficult to change distros when you have many computers/notebooks and
>>>> you want them to share the same distro.
>>>>
>>>> Some of my small scripts and programs need to adapt. It is not a big
>>>> deal, but I want them to keep organized. I think the best way is to
>>>> reorganize them within the parameters and directory structure of a
>>>> slackware package.
>>>>
>>>>
>>>> Please, what is a good updated detailed source of explanation about
>>>> the format and internals of a tgz tar-ball (package)?
>>>>
>>>>
>>>> Thanks and still in time, happy 2022.
>>>
>>>
>>> Welcome! They're pretty simple. The majority of it is simply extracted to the root filesystem and is stored with the exact layout it is expected to have on the root filesystem.
>>>
>>> Where it differs is the install/ directory. This houses the files for the Slackware package manager. The two most common are slack-desc and doinst.sh. The former is used as the information displayed by Slackware's package manager during installation and maintenance. The latter is an optional file that is run immediately after the package is installed. You can see SBo's templates for both at the below address.
>>>
>>> Good luck,
>>> Jeremy
>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at 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 at slackbuilds.org
>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>> FAQ - https://slackbuilds.org/faq/
>>
>

From slackbuilds at ninefamily.com  Thu Jan 13 03:03:11 2022
From: slackbuilds at ninefamily.com (slackbuilds at ninefamily.com)
Date: Wed, 12 Jan 2022 22:03:11 -0500
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <616a6654-52b9-cb17-eae2-4ad8dab6a3c6@ninefamily.com>
References: <616a6654-52b9-cb17-eae2-4ad8dab6a3c6@ninefamily.com>
Message-ID: <4ba301eb-fb29-e2a9-d046-3953951d3ad2@ninefamily.com>


I was going to say do something like Pat does with Firefox but that 
looks like it

cd $(dirname $0) ; CWD=$(pwd)

PKGNAM=mozilla-firefox
VERSION=$(basename $(ls firefox-*.tar.?z | cut -d - -f 2 | rev | cut -f 3- -d . | rev) .source)
RELEASEVER=$(echo $VERSION | cut -f 1 -d r | cut -f 1 -d b | cut -f 1 -d e)
BUILD=${BUILD:-1}

https://ftp.ussg.indiana.edu/linux/slackware/slackware64-current/source/xap/mozilla-firefox/mozilla-firefox.SlackBuild

On 1/10/22 17:17, Konrad J Hambrick wrote:
> Klaatu --
>
> That's pretty much what I do ( source $PROGRAM.info ) in my 
> do-SlackBuild.$PRGNAM scripts.
>
> But I do that in a wrapper-script that invokes the standard SlackBuild.
>
> The Code below is auto-generated by a get-SB-pkg script ( example:? 
> get-SB-pkg intel-microcode )
>
> As you can see, the $PRGNAM.info File is sourced by the wrapper script 
> but I can still override the VERSION as expected:
>
> ?? VERSION=1.2.3.4 ./do-SlackBuild.intel-microcode
>
> One can also set TAG= to append a TAG ( like say, TAG=_kjh )
>
> As a bonus, the do-wrapper logs all the output to 
> $PRGNAM-SlackBuild-$VERSION$TAG.log
>
> Anyhow ... my $0.02 ... no need to change the SlackBuilds ( PLEASE 
> don't change the SlackBuilds :)
>
> -- kjh
>
>     #!/bin/sh
>
>     DoName="intel-microcode.SlackBuild"
>
>     MyVersion="$VERSION"
>
>     . ./intel-microcode.info <http://intel-microcode.info>
>
>     [ "$MyVersion" = "" ] && MyVersion="$VERSION"
>
>     LogNam="$DoName-$MyVersion$TAG.log"
>
>     unset PRGNAM
>     unset VERSION
>     unset HOMEPAGE
>     unset DOWNLOAD
>     unset MD5SUM
>     unset DOWNLOAD_x86_64
>     unset MD5SUM_x86_64
>     unset REQUIRES
>     unset MAINTAINER
>     unset EMAIL
>     #
>     # set and export any extra variables here
>     #
>     export TAG
>     export VERSION="$MyVersion"
>
>     # do the deed
>     #
>     echo "$DoName startup ?at `date`"? |tee ? ?$LogNam
>     ./$DoName 2>&1 ? ? ? ? ? ? ? ? ? ? |tee -a $LogNam
>     #
>     RetCode=${PIPESTATUS[0]}
>     #
>     [ "$RetCode" = "0" ] && RetStr="complete" || RetStr="FAILED ?"
>     #
>     # optional pre-installation instructions ?here
>     #
>     #
>     # optional pre-installation instructions there
>     #
>     # log your results
>     #
>     echo "$DoName $RetStr at `date` ... RetCode = $RetCode" |tee -a
>     $LogNam
>     exit $RetCode
>
>
> On Tue, Jan 4, 2022 at 3:11 PM Klaatu <klaatu at mixedsignals.ml> wrote:
>
>     Why do we define the VERSION for a package in two separate files?
>
>     What if we replaced this line in foo.SlackBuild:
>
>     VERSION={VERSION:-0.0.1}
>
>     with this instead:
>
>     . ./$PRGNAM.info
>
>     The VERSION variable would get imported from a consolidated
>     location (the .info file).
>
>     It seems to make more sense to me, and it makes trivial upgrades
>     (the ones where I go in and just bump a version number to
>     something I want to build) a one-file task.
>
>     Thoughts?
>
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220112/fb941f9c/attachment-0001.htm>

From slackbuilds at ninefamily.com  Thu Jan 13 03:04:01 2022
From: slackbuilds at ninefamily.com (slackbuilds at ninefamily.com)
Date: Wed, 12 Jan 2022 22:04:01 -0500
Subject: [Slackbuilds-users] Fwd:  Howto for slackware tgz
In-Reply-To: <86c5582f-baf0-20cd-0ffc-a01e73833c86@ninefamily.com>
References: <86c5582f-baf0-20cd-0ffc-a01e73833c86@ninefamily.com>
Message-ID: <0b9f5860-9558-ed7e-259a-43688738d5c0@ninefamily.com>


A Slackware _package_ is just an archive and does not have any 
parameters and structure its self in order to keep with the philosophy^1 
of maintaining the software as close to what the original author 
intended and not adding any extra layers or complexity.

A Slack_build_ is a script that is bundled within the package archive 
(tgz) that simply runs the configure/make and install process as 
described in the overview process 
https://docs.slackware.com/slackware:slackbuild_scripts

Imagine you found a software project that was not in the Debian or 
Devuan repositories and wanted to use it on one of your existing 
systems. You would download the source from that project, extract it and 
peruse the documentation to see if it has any dependency requirements 
and if you have everything it requires follow the build and install 
process for that software. That build/install process is what the 
Slackbuild does. The Slackbuild script will have a standard format to 
help with ease of re-use and long term maintenance.

A brief layout of a Slackware install can be found here 
https://docs.slackware.com/slackbook:working_with_filesystems but in 
general it follows what the Linux / Kernel foundation and developers set 
forth as standards, again per the Slackware philosophy

You can extract any Slackware package and see the internal structure is 
that of the software's completed build/install laid out as the software 
author intended.

There are a number of tools to help automate bulk building packages for 
deployment to multiple systems if that's something you are in need of.

1: https://docs.slackware.com/slackware:philosophy

On 1/10/22 21:18, Beco via SlackBuilds-users wrote:
> Hello there, Slack users,
>
> I just joined.
> I hope you are all doing well, and that this list is still active.
>
> I am migrating from Debian systemD. I tried Devuan as well. It is
> difficult to change distros when you have many computers/notebooks and
> you want them to share the same distro.
>
> Some of my small scripts and programs need to adapt. It is not a big
> deal, but I want them to keep organized. I think the best way is to
> reorganize them within the parameters and directory structure of a
> slackware package.
>
>
> Please, what is a good updated detailed source of explanation about
> the format and internals of a tgz tar-ball (package)?
>
>
> Thanks and still in time, happy 2022.
>

From roger.krowiak at gmail.com  Thu Jan 13 07:32:29 2022
From: roger.krowiak at gmail.com (Roger Krowiak)
Date: Thu, 13 Jan 2022 08:32:29 +0100
Subject: [Slackbuilds-users] Slacker reporting for duty
Message-ID: <CAGpsf_EJRbq=Ljr_EG_QjtCVEUjyM4dCD5_=eM+rB=zME4HSNA@mail.gmail.com>

Hi guys,

I've never maintained any app, but I'm willing to help. So, do you have any
*easy going* app to maintain, which I can pick up? Also some mentoring
would be welcome.

I've been using Slackware for a while and I've got moderate BASH skills
too. And - I'm here to help :)

Any ideas?

twitter: @SlavoFreso <https://twitter.com/SlavoFreso>
facebook: Slavomir Freso <http://www.facebook.com/roger.krowiak>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220113/274e2077/attachment.htm>

From ozan.turkyilmaz at gmail.com  Thu Jan 13 08:14:50 2022
From: ozan.turkyilmaz at gmail.com (=?UTF-8?B?T3phbiBUw7xya3nEsWxtYXo=?=)
Date: Thu, 13 Jan 2022 11:14:50 +0300
Subject: [Slackbuilds-users] Slacker reporting for duty
In-Reply-To: <CAGpsf_EJRbq=Ljr_EG_QjtCVEUjyM4dCD5_=eM+rB=zME4HSNA@mail.gmail.com>
References: <CAGpsf_EJRbq=Ljr_EG_QjtCVEUjyM4dCD5_=eM+rB=zME4HSNA@mail.gmail.com>
Message-ID: <CA+da1opZ9th2HNRWoKMSJitB9N=OJMT8J0hUrupdUHPeKE7MFg@mail.gmail.com>

Roger Krowiak <roger.krowiak at gmail.com>, 13 Oca 2022 Per, 10:32 tarihinde
?unu yazd?:

> Hi guys,
>
> I've never maintained any app, but I'm willing to help. So, do you have
> any *easy going* app to maintain, which I can pick up? Also some mentoring
> would be welcome.
>
> I've been using Slackware for a while and I've got moderate BASH skills
> too. And - I'm here to help :)
>
> Any ideas?
>

I am always looking for someone to take over ibus-anthy and emule off me. I
don't know if they are good choices for a start.

Regards,
Ozan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220113/feae159d/attachment.htm>

From kingbeowulf at gmail.com  Sun Jan 16 02:22:30 2022
From: kingbeowulf at gmail.com (King Beowulf)
Date: Sat, 15 Jan 2022 18:22:30 -0800
Subject: [Slackbuilds-users] Slacker reporting for duty
In-Reply-To: <CAGpsf_EJRbq=Ljr_EG_QjtCVEUjyM4dCD5_=eM+rB=zME4HSNA@mail.gmail.com>
References: <CAGpsf_EJRbq=Ljr_EG_QjtCVEUjyM4dCD5_=eM+rB=zME4HSNA@mail.gmail.com>
Message-ID: <af0175b4-bc92-0077-0c43-2f0ea0270587@gmail.com>

On 1/12/22 23:32, Roger Krowiak wrote:
> Hi guys,
> 
> I've never maintained any app, but I'm willing to help. So, do you have
> any *easy going* app to maintain, which I can pick up? Also some
> mentoring would be welcome.
> 
> I've been using Slackware for a while and I've got moderate BASH skills
> too. And - I'm here to help :)
> 
> Any ideas?
> 
>

The best app to start with is one you actually use but isn't already in
SBo or Slackware. Or, take over one that is listed as unmaintained or
abandoned (except for those dropped by upstream devs!).

you can poke around here:
https://git.slackbuilds.org/slackbuilds/

and peruse the "pending-removal" branch.

-KB




-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature
Type: application/pgp-signature
Size: 203 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220115/acdea1bd/attachment.asc>

From dchmelik at gmail.com  Thu Jan 20 08:17:47 2022
From: dchmelik at gmail.com (David Chmelik)
Date: Thu, 20 Jan 2022 00:17:47 -0800
Subject: [Slackbuilds-users] Slacker reporting for duty
Message-ID: <eb3452f6-4d17-97af-0d35-ba48dd7a542a@gmail.com>

On Wed, 12 Jan 2022 at 23:32, Roger Krowiak <roger.krowiak at gmail.com> wrote:

    Hi guys,

    I've never maintained any app, but I'm willing to help. So, do you
    have any *easy going* app to maintain, which I can pick up? Also
    some mentoring would be welcome.

    I've been using Slackware for a while and I've got moderate BASH
    skills too. And - I'm here to help :)

    Any ideas?


I think one SlackBuild being removed for 15 (still useful) is 
gtk-chtheme, which the maintainer told me he quit (probably forwarded 
here) but also suggested newer similar programs like lx-appearance.? I 
refused to take over because until I program graphical user interfaces 
(GUI,) I avoid maintaining/fixing GUI SlackBuilds, but a GTK theme 
changer could be considered important (GTK, Qt being the top two GUI 
libraries used in many/most X, KDE & etc. programs.)
 ??? Last year I offered anyone can take over roguelike games Angband 
and perhaps Dungeon Crawl Stone Soup (DCSS) as they changed too much 
(for my liking.)? I'd then make 'angband-retro.' Actually I heard you 
can still play removed fantasy races in DCSS, not scoreable (fine, but 
it seems they always remove stuff and replace with something simpler or 
bizarre) so I'm not entirely sure I'm giving up DCSS (maybe for a 
roguelike game enthusiast.)

David (Darwin(Elf))


From dchmelik at gmail.com  Thu Jan 20 08:17:57 2022
From: dchmelik at gmail.com (David Chmelik)
Date: Thu, 20 Jan 2022 00:17:57 -0800
Subject: [Slackbuilds-users] Slacker reporting for duty
Message-ID: <879bd2d4-8c32-6d98-d609-70d371e3189d@gmail.com>

On Wed, 12 Jan 2022 at 23:32, Roger Krowiak <roger.krowiak at gmail.com> wrote:

    Hi guys,

    I've never maintained any app, but I'm willing to help. So, do you
    have any *easy going* app to maintain, which I can pick up? Also
    some mentoring would be welcome.

    I've been using Slackware for a while and I've got moderate BASH
    skills too. And - I'm here to help :)

    Any ideas?


I think one SlackBuild being removed for 15 (still useful) is 
gtk-chtheme, which the maintainer told me he quit (probably forwarded 
here) but also suggested newer similar programs like lx-appearance.? I 
refused to take over because until I program graphical user interfaces 
(GUI,) I avoid maintaining/fixing GUI SlackBuilds, but a GTK theme 
changer could be considered important (GTK, Qt being the top two GUI 
libraries used in many/most X, KDE & etc. programs.)
 ??? Last year I offered anyone can take over roguelike games Angband 
and perhaps Dungeon Crawl Stone Soup (DCSS) as they changed too much 
(for my liking.)? I'd then make 'angband-retro.' Actually I heard you 
can still play removed fantasy races in DCSS, not scoreable (fine, but 
it seems they always remove stuff and replace with something simpler or 
bizarre) so I'm not entirely sure I'm giving up DCSS (maybe for a 
roguelike game enthusiast.)

David (Darwin(Elf))


From didier at slint.fr  Sun Jan 23 22:44:19 2022
From: didier at slint.fr (Didier Spaier)
Date: Sun, 23 Jan 2022 23:44:19 +0100
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
In-Reply-To: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
References: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
Message-ID: <9fe2d7e0-8bb0-acb7-5c6a-027aa9906a1a@slint.fr>

Hello, reminder and follow-up below:

Le 07/01/2022 ? 19:54, Didier Spaier a ?crit?:
> I don't have the time to properly maintain them, in addition to Slint maintenance.
> 
> List:
> abcde
> bdf2psf
> bicon
> cd-discid
> doclifter
> espeakup
> gksu
> libdca
> libgksu
> libgtop
> libshout
> mkcue
> perl-Encode-EUCJPASCII
> perl-Encode-HanExtra
> perl-Encode-ISO2022
> perl-Encode-JISX0213
> perl-MIME-Charset
> perl-MusicBrainz-DiscID
> perl-Text-CharWidth
> perl-Text-WrapI18N
> perl-Unicode-LineBreak
> perl-WebService-MusicBrainz
> po4a
> qControlCenter
> txt2tags

If I remember correctly, following SlackBuilds have not be claimed yet:

espeakup
gksu
libdca => optional dep of vlc, MPlayer and xine-lib
libgksu
libshout => optional dep of vlc and mpd-sacd
qControlCenter

Also, I have transferred upstream maintenance of qControlCenter to Dimitris
Tzemos (Slackel maintainer), so its new upstream repository is:
https://github.com/djemos/qControlCenter
As Dimitris has ported qControlCenter to python3 and PyQt5 it should be ready
for Slackware 15 (he ships qControlCenter in Slackel which is based on
Slackware-current).

Cheers,
Didier

From chris.willing at linux.com  Sun Jan 23 23:19:13 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Mon, 24 Jan 2022 09:19:13 +1000
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
In-Reply-To: <9fe2d7e0-8bb0-acb7-5c6a-027aa9906a1a@slint.fr>
References: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
 <9fe2d7e0-8bb0-acb7-5c6a-027aa9906a1a@slint.fr>
Message-ID: <0b26181e-66b9-7ecb-905d-4c6a5611a665@linux.com>

On 1/24/22 08:44, Didier Spaier wrote:
> Hello, reminder and follow-up below:
> 
> Le 07/01/2022 ? 19:54, Didier Spaier a ?crit?:
>> I don't have the time to properly maintain them, in addition to Slint maintenance.
>>
>> List:
>> abcde
>> bdf2psf
>> bicon
>> cd-discid
>> doclifter
>> espeakup
>> gksu
>> libdca
>> libgksu
>> libgtop
>> libshout
>> mkcue
>> perl-Encode-EUCJPASCII
>> perl-Encode-HanExtra
>> perl-Encode-ISO2022
>> perl-Encode-JISX0213
>> perl-MIME-Charset
>> perl-MusicBrainz-DiscID
>> perl-Text-CharWidth
>> perl-Text-WrapI18N
>> perl-Unicode-LineBreak
>> perl-WebService-MusicBrainz
>> po4a
>> qControlCenter
>> txt2tags
> 
> If I remember correctly, following SlackBuilds have not be claimed yet:
> 
> espeakup
> gksu
> libdca => optional dep of vlc, MPlayer and xine-lib
> libgksu
> libshout => optional dep of vlc and mpd-sacd
> qControlCenter
> 

OK since they are deps of vlc, I'll claim libdca & libshout.

Thanks for your work maintaining them until now.

chris

From didier at slint.fr  Sun Jan 23 23:49:16 2022
From: didier at slint.fr (Didier Spaier)
Date: Mon, 24 Jan 2022 00:49:16 +0100
Subject: [Slackbuilds-users] My SlackBuilds are up for grabs
In-Reply-To: <0b26181e-66b9-7ecb-905d-4c6a5611a665@linux.com>
References: <5d451406-509e-c7f1-a89b-9565cab894b1@slint.fr>
 <9fe2d7e0-8bb0-acb7-5c6a-027aa9906a1a@slint.fr>
 <0b26181e-66b9-7ecb-905d-4c6a5611a665@linux.com>
Message-ID: <6c8ae20b-0f3e-90d2-c463-3388f25ea141@slint.fr>

Le 24/01/2022 ? 00:19, Christoph Willing a ?crit?:
> OK since they are deps of vlc, I'll claim libdca & libshout.
> 
> Thanks for your work maintaining them until now.

Thanks for you work maintaining vlc (and also mpv, both shipped in Slint).

Didier

From chris.willing at linux.com  Sat Jan 29 10:09:07 2022
From: chris.willing at linux.com (Christoph Willing)
Date: Sat, 29 Jan 2022 20:09:07 +1000
Subject: [Slackbuilds-users] uid/gid for flatpak
Message-ID: <72863b66-c860-587c-0e42-66ff5b80f5ce@linux.com>

An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220129/e5b546d1/attachment.htm>

From sb at rbn.im  Sun Jan 30 17:46:08 2022
From: sb at rbn.im (Ruben Schuller)
Date: Sun, 30 Jan 2022 18:46:08 +0100
Subject: [Slackbuilds-users] anyone interested in maintaining
 gajim/python-nbxmpp?
In-Reply-To: <20210520013130.6e34bc4c@kirsche.kuchen>
References: <20210519233556.58ce3dde@kirsche.kuchen>
 <7f129c5e1581cbcad71d2d73dba9fecd@linux.com>
 <20210520013130.6e34bc4c@kirsche.kuchen>
Message-ID: <20220130184608.1aa11457@kiwi.kuchen>

Hi Gerardo, hi list!

I updated Gajim (and python-nbxmpp) to the latest version. Both seem to
work fine on -current, but I can't really test them as I don't have a
Jabber account anymore. Please see the attached tarballs. I still
release maintenance to Gerardo if he still wants it, it should be a
bit easier now that it's updated :)

2021-05-20 Ruben Schuller <sb at rbn.im>:

> hi gerardo!
> 
> 2021-05-19 Gerardo Zamudio <gerardo.zamudio at linux.com>:
> 
> > I will gladly take it. I use Gajim every single day.  
> 
> nice, it will be in better care than i can provide currently :)

Cheers
Ruben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gajim.tar.gz
Type: application/gzip
Size: 2698 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220130/6c243f0d/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: python-nbxmpp.tar.gz
Type: application/gzip
Size: 2477 bytes
Desc: not available
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220130/6c243f0d/attachment-0001.bin>

From zhu.qunying at gmail.com  Sun Jan 30 19:13:09 2022
From: zhu.qunying at gmail.com (Qun-Ying)
Date: Sun, 30 Jan 2022 11:13:09 -0800
Subject: [Slackbuilds-users] two packages needs new mainterner
Message-ID: <CAHiy0bSJaPqYr_zijTCPaGSq0QfWz0JbcwrM9AhL2AX24wcpqg@mail.gmail.com>

Hi,

I no longer making use of these two packages, hence it is not updated
for a long time:
network/guacamole-client
network/guacamole-server

Anyone interest to take over the ownership?

-- 
Qun-Ying

From andrew.clemons at gmail.com  Mon Jan 31 09:54:58 2022
From: andrew.clemons at gmail.com (Andrew Clemons)
Date: Mon, 31 Jan 2022 22:54:58 +1300
Subject: [Slackbuilds-users] anyone interested in maintaining
 gajim/python-nbxmpp?
In-Reply-To: <20220130184608.1aa11457@kiwi.kuchen>
References: <20210519233556.58ce3dde@kirsche.kuchen>
 <7f129c5e1581cbcad71d2d73dba9fecd@linux.com>
 <20210520013130.6e34bc4c@kirsche.kuchen>
 <20220130184608.1aa11457@kiwi.kuchen>
Message-ID: <Yfex8qTeQg0mbVkU@gmail.com>

On 2022-01-30 18:46:08 +0100, sb at rbn.im wrote:
> Hi Gerardo, hi list!
>
> I updated Gajim (and python-nbxmpp) to the latest version. Both seem to
> work fine on -current, but I can't really test them as I don't have a
> Jabber account anymore. Please see the attached tarballs. I still
> release maintenance to Gerardo if he still wants it, it should be a
> bit easier now that it's updated :)

Thanks Ruben. I also use Gajim, so I have updated these on my branch,
replacing some local changes I had been using for 1.x releases. Your
changes are working fine here. If I don't hear from Gerardo by the time
there is a new Gajim release, then I will take over maintenance of these
two.

Cheers,
Andrew

From enine at ninefamily.com  Mon Jan 10 22:39:34 2022
From: enine at ninefamily.com (Eugene Nine)
Date: Mon, 10 Jan 2022 22:39:34 -0000
Subject: [Slackbuilds-users] What if we `source`d the version number
In-Reply-To: <CANBHt+MkJLdqUha3WYNDYRx1uRjCV_=d0tJKaFEXJDCNrObBeg@mail.gmail.com>
References: <4575009.ea4tHpRPHW@beast>
 <CANBHt+MkJLdqUha3WYNDYRx1uRjCV_=d0tJKaFEXJDCNrObBeg@mail.gmail.com>
Message-ID: <616a6654-52b9-cb17-eae2-4ad8dab6a3c6@ninefamily.com>

I was going to say do something like Pat does with Firefox but that 
looks like it

cd $(dirname $0) ; CWD=$(pwd)

PKGNAM=mozilla-firefox
VERSION=$(basename $(ls firefox-*.tar.?z | cut -d - -f 2 | rev | cut -f 3- -d . | rev) .source)
RELEASEVER=$(echo $VERSION | cut -f 1 -d r | cut -f 1 -d b | cut -f 1 -d e)
BUILD=${BUILD:-1}

https://ftp.ussg.indiana.edu/linux/slackware/slackware64-current/source/xap/mozilla-firefox/mozilla-firefox.SlackBuild

On 1/10/22 17:17, Konrad J Hambrick wrote:
> Klaatu --
>
> That's pretty much what I do ( source $PROGRAM.info ) in my 
> do-SlackBuild.$PRGNAM scripts.
>
> But I do that in a wrapper-script that invokes the standard SlackBuild.
>
> The Code below is auto-generated by a get-SB-pkg script ( example:? 
> get-SB-pkg intel-microcode )
>
> As you can see, the $PRGNAM.info File is sourced by the wrapper script 
> but I can still override the VERSION as expected:
>
> ?? VERSION=1.2.3.4 ./do-SlackBuild.intel-microcode
>
> One can also set TAG= to append a TAG ( like say, TAG=_kjh )
>
> As a bonus, the do-wrapper logs all the output to 
> $PRGNAM-SlackBuild-$VERSION$TAG.log
>
> Anyhow ... my $0.02 ... no need to change the SlackBuilds ( PLEASE 
> don't change the SlackBuilds :)
>
> -- kjh
>
>     #!/bin/sh
>
>     DoName="intel-microcode.SlackBuild"
>
>     MyVersion="$VERSION"
>
>     . ./intel-microcode.info <http://intel-microcode.info>
>
>     [ "$MyVersion" = "" ] && MyVersion="$VERSION"
>
>     LogNam="$DoName-$MyVersion$TAG.log"
>
>     unset PRGNAM
>     unset VERSION
>     unset HOMEPAGE
>     unset DOWNLOAD
>     unset MD5SUM
>     unset DOWNLOAD_x86_64
>     unset MD5SUM_x86_64
>     unset REQUIRES
>     unset MAINTAINER
>     unset EMAIL
>     #
>     # set and export any extra variables here
>     #
>     export TAG
>     export VERSION="$MyVersion"
>
>     # do the deed
>     #
>     echo "$DoName startup ?at `date`"? |tee ? ?$LogNam
>     ./$DoName 2>&1 ? ? ? ? ? ? ? ? ? ? |tee -a $LogNam
>     #
>     RetCode=${PIPESTATUS[0]}
>     #
>     [ "$RetCode" = "0" ] && RetStr="complete" || RetStr="FAILED ?"
>     #
>     # optional pre-installation instructions ?here
>     #
>     #
>     # optional pre-installation instructions there
>     #
>     # log your results
>     #
>     echo "$DoName $RetStr at `date` ... RetCode = $RetCode" |tee -a
>     $LogNam
>     exit $RetCode
>
>
> On Tue, Jan 4, 2022 at 3:11 PM Klaatu <klaatu at mixedsignals.ml> wrote:
>
>     Why do we define the VERSION for a package in two separate files?
>
>     What if we replaced this line in foo.SlackBuild:
>
>     VERSION={VERSION:-0.0.1}
>
>     with this instead:
>
>     . ./$PRGNAM.info
>
>     The VERSION variable would get imported from a consolidated
>     location (the .info file).
>
>     It seems to make more sense to me, and it makes trivial upgrades
>     (the ones where I go in and just bump a version number to
>     something I want to build) a one-file task.
>
>     Thoughts?
>
>     _______________________________________________
>     SlackBuilds-users mailing list
>     SlackBuilds-users at 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 at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives -https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ -https://slackbuilds.org/faq/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20220110/3521c138/attachment-0001.htm>

From enine at ninefamily.com  Tue Jan 11 03:15:59 2022
From: enine at ninefamily.com (Eugene Nine)
Date: Tue, 11 Jan 2022 03:15:59 -0000
Subject: [Slackbuilds-users] Howto for slackware tgz
In-Reply-To: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>
References: <CALuYw2x+ay8n8s1txJrtDxM3CDCU9xUKU+cM36dabdY6fhRBGg@mail.gmail.com>
Message-ID: <86c5582f-baf0-20cd-0ffc-a01e73833c86@ninefamily.com>

A Slackware _package_ is just an archive and does not have any 
parameters and structure its self in order to keep with the philosophy^1 
of maintaining the software as close to what the original author 
intended and not adding any extra layers or complexity.

A Slack_build_ is a script that is bundled within the package archive 
(tgz) that simply runs the configure/make and install process as 
described in the overview process 
https://docs.slackware.com/slackware:slackbuild_scripts

Imagine you found a software project that was not in the Debian or 
Devuan repositories and wanted to use it on one of your existing 
systems. You would download the source from that project, extract it and 
peruse the documentation to see if it has any dependency requirements 
and if you have everything it requires follow the build and install 
process for that software. That build/install process is what the 
Slackbuild does. The Slackbuild script will have a standard format to 
help with ease of re-use and long term maintenance.

A brief layout of a Slackware install can be found here 
https://docs.slackware.com/slackbook:working_with_filesystems but in 
general it follows what the Linux / Kernel foundation and developers set 
forth as standards, again per the Slackware philosophy

You can extract any Slackware package and see the internal structure is 
that of the software's completed build/install laid out as the software 
author intended.

There are a number of tools to help automate bulk building packages for 
deployment to multiple systems if that's something you are in need of.

1: https://docs.slackware.com/slackware:philosophy

On 1/10/22 21:18, Beco via SlackBuilds-users wrote:
> Hello there, Slack users,
>
> I just joined.
> I hope you are all doing well, and that this list is still active.
>
> I am migrating from Debian systemD. I tried Devuan as well. It is
> difficult to change distros when you have many computers/notebooks and
> you want them to share the same distro.
>
> Some of my small scripts and programs need to adapt. It is not a big
> deal, but I want them to keep organized. I think the best way is to
> reorganize them within the parameters and directory structure of a
> slackware package.
>
>
> Please, what is a good updated detailed source of explanation about
> the format and internals of a tgz tar-ball (package)?
>
>
> Thanks and still in time, happy 2022.
>