Re: [Slackbuilds-users] Please your support
Just make his projects your star On Mon, 18 Apr 2022, 07:59 Klaatu, wrote: > I don't find this spammy. Were he a stranger, I would feel differently, > but Dimitris maintains several SlackBuild scripts: > > https://slackbuilds.org/advsearch.php?q=Zlatanidis=maint > > He also produces a very useful tool `slpkg` (among others) for use with > SBo. > > Is seems reasonable to ask other users of SBo to take a moment to click > what is essentially a "Like" button, so that his prospective employer sees > that his work online actually has an impact on people. > > Personally I hope Dimitris gets the job he's applying for, and is well > paid, and can continue to work on SBo and SBo-related tools well into the > future. > > Imaginary Internet Stars are mostly free (clicking buttons took about 5 > minutes of my time), so I've given him a bunch. > > > ___ > 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] Please your support
I don't find this spammy. Were he a stranger, I would feel differently, but Dimitris maintains several SlackBuild scripts: https://slackbuilds.org/advsearch.php?q=Zlatanidis=maint He also produces a very useful tool `slpkg` (among others) for use with SBo. Is seems reasonable to ask other users of SBo to take a moment to click what is essentially a "Like" button, so that his prospective employer sees that his work online actually has an impact on people. Personally I hope Dimitris gets the job he's applying for, and is well paid, and can continue to work on SBo and SBo-related tools well into the future. Imaginary Internet Stars are mostly free (clicking buttons took about 5 minutes of my time), so I've given him a bunch. ___ 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] Please your support
That looks pretty spam-ish, then. Let's hope other unrelated MLs were not hit by the same thing. On Sun, 17 Apr 2022 at 23:09, Jeremy Hansen wrote: > On Sun, Apr 17, 2022, 9:06 PM Francois Gingras > wrote: > >> Are you seriously asking us to commit to your gitlab? Can you grab a few >> projects yourself and commit those on your own? >> >> >> On Sun, 17 Apr 2022 at 23:04, Frank Gingras wrote: >> >>> Are you seriously asking us to commit to your gitlab? Can you do grab a >>> few projects yourself and commit those on your own? >>> >>> On Sun, 17 Apr 2022 at 13:54, Dimitris Zlatanidis < >>> d.zlatani...@gmail.com> wrote: >>> Greetings to all members, I would like to ask for your support. I'm giving a job interview (Python Developer) and my Gitlab repository, will play an important role, so whoever wants to add an asterisk in my Projects and especially in slpkg, colored, sun, dropbox-filemanager, sbo-templates etc., I would appreciate it a lot! Thank you very much, Dimitris -- Dimitris Zlatanidis https://dslackw.gitlab.io/slpkg/ https://gitlab.com/dslackw >>> > No, I think he's asking us to "star" or basically favorite his projects if > you've think they've been helpful to you. > > Jeremy > ___ > 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] Please your support
On Sun, Apr 17, 2022, 9:06 PM Francois Gingras wrote: > Are you seriously asking us to commit to your gitlab? Can you grab a few > projects yourself and commit those on your own? > > > On Sun, 17 Apr 2022 at 23:04, Frank Gingras wrote: > >> Are you seriously asking us to commit to your gitlab? Can you do grab a >> few projects yourself and commit those on your own? >> >> On Sun, 17 Apr 2022 at 13:54, Dimitris Zlatanidis >> wrote: >> >>> Greetings to all members, >>> >>> I would like to ask for your support. >>> I'm giving a job interview (Python Developer) and my Gitlab repository, >>> will play an important role, so whoever wants to add an asterisk in my >>> Projects and especially in slpkg, colored, sun, dropbox-filemanager, >>> sbo-templates etc., I would appreciate it a lot! >>> >>> Thank you very much, >>> Dimitris >>> >>> -- >>> Dimitris Zlatanidis >>> https://dslackw.gitlab.io/slpkg/ >>> https://gitlab.com/dslackw >>> >> No, I think he's asking us to "star" or basically favorite his projects if you've think they've been helpful to you. Jeremy ___ 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] Please your support
Are you seriously asking us to commit to your gitlab? Can you grab a few projects yourself and commit those on your own? On Sun, 17 Apr 2022 at 23:04, Frank Gingras wrote: > Are you seriously asking us to commit to your gitlab? Can you do grab a > few projects yourself and commit those on your own? > > On Sun, 17 Apr 2022 at 13:54, Dimitris Zlatanidis > wrote: > >> Greetings to all members, >> >> I would like to ask for your support. >> I'm giving a job interview (Python Developer) and my Gitlab repository, >> will play an important role, so whoever wants to add an asterisk in my >> Projects and especially in slpkg, colored, sun, dropbox-filemanager, >> sbo-templates etc., I would appreciate it a lot! >> >> Thank you very much, >> Dimitris >> >> -- >> Dimitris Zlatanidis >> https://dslackw.gitlab.io/slpkg/ >> https://gitlab.com/dslackw >> >> ___ >> 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] 'Correct' download link from Github?
This is a very common. I think it would be nice to add an example of David's answer to the SlackBuild templates for both new and experienced maintainers. I've wasted countless minutes looking up the "secret formula" when starting or updating my scripts. On 17 April 2022 8:33:33 AM UTC, Dave Woodfall wrote: >On 17/04/22 18:08, >andrew put forth the proposition: >> I am putting a new Slackbuild together for opustags, which is hosted >> on github: >> https://github.com/fmang/opustags >> I am a little unsure of the correct download link from github which >> shows some variation whether wget or browser is used. >> Is there an SBo policy about such links? > >No policy yet AFAIK but you can find the release tag (add /tags/ to >the end of the URL) and then do something like: > >URL/archive/TAG/PRGNAM-TAG.tar.gz which would be: > >https://github.com/fmang/opustags/archive/1.2.3/opustags-1.2.3.tar.gz > >or > >https://github.com/fmang/opustags/archive/v1.2.3/opustags-1.2.3.tar.gz > >(note the v before the first TAG sometimes works if the first URL >gives a 404.) > >The downloaded tarball can be tested with `tar tf | head' >to see if the directory name really matches the expected version >number. > >HTH > >-- >Dave >___ >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/ > -- Klaatu ___ 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] THE.SlackBuild
On Sun, 17 Apr 2022, B. Watson wrote: > On Sun, 17 Apr 2022, Richard Narron wrote: > > > For example after reading the THE install document, I know that the program > > has a text ncurses version, a graphical X11 version and that it runs on > > Red Hat Linux. > > README doesn't say anything about Red Hat, but that's not particularly > useful information to include in a Slackware package anyway. It does > say "most Unix systems". I don't judge information and I do not presume to know what a user might or might not be interested in. When I look on my system I find over 500 "INSTALL" documents in the /usr/doc directory. Richard Narron ___ 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] Please your support
Greetings to all members, I would like to ask for your support. I'm giving a job interview (Python Developer) and my Gitlab repository, will play an important role, so whoever wants to add an asterisk in my Projects and especially in slpkg, colored, sun, dropbox-filemanager, sbo-templates etc., I would appreciate it a lot! Thank you very much, Dimitris -- Dimitris Zlatanidis https://dslackw.gitlab.io/slpkg/ https://gitlab.com/dslackw ___ 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] 'Correct' download link from Github?
On 17/04/22 14:42,
Ruben Schuller put forth the proposition:
> Hi,
> 2022-04-17 Ozan Türkyılmaz :
> > Paz, 2022-04-17 tarihinde 09:33 +0100 saatinde, Dave Woodfall yazdı:
> > > No policy yet AFAIK but you can find the release tag (add /tags/ to
> > > the end of the URL) and then do something like:
> > >
> > >
> > I remember a talk about content disposition (and how wget ignores it
> > by default) and github links should give same file with or without
> > content disposition. I dont remember when thou. My memory is not as
> > it used to be.
I think what you're referring to is that github will tend to send any
name tarball that you ask for from some links, but using the release
source links sends the format 1.2.3.tar.gz by default. This isn't
very useful if you use sbopkg and /var/cache/sbopkg fills up with
1.2.3.tar.gz, 3.4.5.tar.gz etc., because at some point you might need
to find some source and seeing them named like that is unhelpful.
> I think the decision was that scripts should assume content disposition
> is used. I usually use
> tar xvf v${VERSION}.tar.gz || tar ${PRGNAM}-${VERSION}.tar.gz
> (or the other way around..) in my scripts to catch the case when it
> isn't. I think it's fine, either of those tarballs should be MD5-checked
We can't assume that it is always used. Content-Disposition doesn't
always work, and is still marked as experimental in wget(1), and in
curl can give errors when mixed with other flags like -C.
"--content-disposition
If this is set to on, experimental (not fully-functional) support for
"Content-Disposition" headers is enabled. This can currently result in
extra round-trips to the server for a "HEAD" request, and is known to
suffer from a few bugs, which is why it is not currently enabled by
default."
The method I showed should always download $PRGNAM-$VERSION.tar.gz
and I change github URLs in submissions when I come across one.
One simple way to do this (test without -i first):
source the .info
sed -E
"s,(https://github.com/[^/]+/$PRGNAM)/archive/refs/tags/v?($VERSION)(.tar.gz),\1/archive/v\2/$PRGNAM-\2\3,"
-i $PRGNAM.info
--
Dave
___
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] THE.SlackBuild
On Sun, 17 Apr 2022, Richard Narron wrote: For example after reading the THE install document, I know that the program has a text ncurses version, a graphical X11 version and that it runs on Red Hat Linux. The README already tells you two of those things: That there's a "text mode and native X11 application", and "THE uses curses as its screen handler". README doesn't say anything about Red Hat, but that's not particularly useful information to include in a Slackware package anyway. It does say "most Unix systems". ___ 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] THE.SlackBuild
On Sat, 16 Apr 2022, Richard Narron wrote: But when it was installed, the first line leaves out the INSTALL document: install -m0644 COPYING FAQ HISTORY README* TODO \ Here is a patch to correct the installed THE.SlackBuild: The INSTALL file is probably being left out on purpose. Have you read it? It's useless for a package user. It describes how to compile THE, or install it from RPMs. However, if you already installed THE from a package built by the SBo script, there's no need to read the INSTALL document: the SBo script already compiled the software for you. This is true of pretty much every INSTALL file (or INSTALL.txt, INSTALL.md) in almost every package. *Rarely*, there's also some useful config/setup information in INSTALL, but in general, SBo packages shouldn't include install instructions. ___ 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] THE.SlackBuild
On Sun, 17 Apr 2022, Dave Woodfall wrote: > On 16/04/22 13:54, > Richard Narron put forth the proposition: > > I recently submitted a new THE.SlackBuild script that copied > > documentation from the install directory like this: > > install -m0644 COPYING FAQ HISTORY INSTALL README* TODO \ > > $PKG/usr/doc/$PRGNAM-$VERSION > > But when it was installed, the first line leaves out the INSTALL document: > > install -m0644 COPYING FAQ HISTORY README* TODO \ > > We don't really need INSTALL documents, because it's already > installed by the time anyone reads it, right? Install documents gives information about what can be installed as well as where it can be installed. For example after reading the THE install document, I know that the program has a text ncurses version, a graphical X11 version and that it runs on Red Hat Linux. Richard ___ 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] 'Correct' download link from Github?
Hi,
2022-04-17 Ozan Türkyılmaz :
> Paz, 2022-04-17 tarihinde 09:33 +0100 saatinde, Dave Woodfall yazdı:
> > No policy yet AFAIK but you can find the release tag (add /tags/ to
> > the end of the URL) and then do something like:
> >
> >
> I remember a talk about content disposition (and how wget ignores it
> by default) and github links should give same file with or without
> content disposition. I dont remember when thou. My memory is not as
> it used to be.
I think the decision was that scripts should assume content disposition
is used. I usually use
tar xvf v${VERSION}.tar.gz || tar ${PRGNAM}-${VERSION}.tar.gz
(or the other way around..) in my scripts to catch the case when it
isn't. I think it's fine, either of those tarballs should be MD5-checked
anyway.
Cheers
Ruben
___
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] 'Correct' download link from Github?
Paz, 2022-04-17 tarihinde 09:33 +0100 saatinde, Dave Woodfall yazdı: > No policy yet AFAIK but you can find the release tag (add /tags/ to > the end of the URL) and then do something like: > > I remember a talk about content disposition (and how wget ignores it by default) and github links should give same file with or without content disposition. I dont remember when thou. My memory is not as it used to be. Regards, Ozan ___ 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] 'Correct' download link from Github?
On Sun, Apr 17, 2022 at 09:33:33AM +0100, Dave Woodfall wrote: > No policy yet AFAIK but you can find the release tag (add /tags/ to > the end of the URL) and then do something like: > > URL/archive/TAG/PRGNAM-TAG.tar.gz which would be: > > https://github.com/fmang/opustags/archive/1.2.3/opustags-1.2.3.tar.gz Thanks, this one worked perfectly :) Andrew -- You think that's air you're breathing now? ___ 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] 'Correct' download link from Github?
On 17/04/22 18:08, andrew put forth the proposition: > I am putting a new Slackbuild together for opustags, which is hosted > on github: > https://github.com/fmang/opustags > I am a little unsure of the correct download link from github which > shows some variation whether wget or browser is used. > Is there an SBo policy about such links? No policy yet AFAIK but you can find the release tag (add /tags/ to the end of the URL) and then do something like: URL/archive/TAG/PRGNAM-TAG.tar.gz which would be: https://github.com/fmang/opustags/archive/1.2.3/opustags-1.2.3.tar.gz or https://github.com/fmang/opustags/archive/v1.2.3/opustags-1.2.3.tar.gz (note the v before the first TAG sometimes works if the first URL gives a 404.) The downloaded tarball can be tested with `tar tf | head' to see if the directory name really matches the expected version number. HTH -- Dave ___ 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] 'Correct' download link from Github?
I am putting a new Slackbuild together for opustags, which is hosted on github: https://github.com/fmang/opustags I am a little unsure of the correct download link from github which shows some variation whether wget or browser is used. Is there an SBo policy about such links? Thanks, Andrew -- You think that's air you're breathing now? ___ 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] THE.SlackBuild
On 16/04/22 13:54, Richard Narron put forth the proposition: > I recently submitted a new THE.SlackBuild script that copied > documentation from the install directory like this: > install -m0644 COPYING FAQ HISTORY INSTALL README* TODO \ > $PKG/usr/doc/$PRGNAM-$VERSION > But when it was installed, the first line leaves out the INSTALL document: > install -m0644 COPYING FAQ HISTORY README* TODO \ > ... > Please advise. > Richard Narron We don't really need INSTALL documents, because it's already installed by the time anyone reads it, right? -- Dave ___ 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/
