Re: [Slackbuilds-users] 'wayland-egl' can be removed from SBO
On Thu, Apr 16, 2020 at 05:51:19PM -0400, Logan Rathbone wrote: > Hello all, > > Now that Diniz Bortlotto has updated wayland to 1.18.0, wayland-egl can > be removed from SBo, as this is now part of wayland and is no longer a > separate project. > > Thanks, > Logan "Poprocks" Fine with me. Cheers ... Duncan. ___ 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] Request to Matteo
Matteo, can you please remove dvdbackup from your slackware-current repo? With Pat upgrading libdvdread to 6.1.1 it is now completely broken. I have been working to try to get the old versions in as static libs, but so far no luck. Thanks. ___ 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] Builds in search of a maintainer
On Thu, 16 Apr 2020, B Watson wrote: > On 4/16/20, Alexander Verbovetsky wrote: > >> python/pycdio > > > > I could take this because it's a dependency of whipper. > I went ahead and changed the .info file in my git branch, so you don't > have to do anything right now. Thank you! I already submitted an update to the pending queue. Best regards, Alexander ___ 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] 'wayland-egl' can be removed from SBO
Hello all, Now that Diniz Bortlotto has updated wayland to 1.18.0, wayland-egl can be removed from SBo, as this is now part of wayland and is no longer a separate project. Thanks, Logan "Poprocks" ___ 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] Builds in search of a maintainer
On 4/16/20, Alexander Verbovetsky wrote: >> python/pycdio > > I could take this because it's a dependency of whipper. Thanks. I went ahead and changed the .info file in my git branch, so you don't have to do anything right 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] Builds in search of a maintainer
Hello, > In August 2019, Dugan Chen orphaned all his builds... some of them > have been picked up by other maintainers (including me), but there are > still quite a few left: > python/pycdio I could take this because it's a dependency of whipper. Best regards, Alexander ___ 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] Builds in search of a maintainer
In August 2019, Dugan Chen orphaned all his builds... some of them have been picked up by other maintainers (including me), but there are still quite a few left: audio/rubyripper desktop/compiz-boxmenu development/gnome-inform7 graphics/vulkan-sdk-bin libraries/gtkglextmm multimedia/munt python/pycdio python/pygpgme ruby/rubygem-atk ruby/rubygem-cairo ruby/rubygem-gdk_pixbuf2 ruby/rubygem-glib2 ruby/rubygem-gtk2 ruby/rubygem-pango ruby/rubygem-pkg-config system/GentiumPlus system/ds4drv system/xnp2 I'd say whoever takes rubyripper should also take the rubygem-* builds, since they're (optional) dependencies of it. Anyone want any of these? ___ 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] 32-bit programs, required to maintain?
Ok thanks, that clears it up. On Thu, 16 Apr 2020, B Watson wrote: On 4/16/20, Andrew Payne wrote: Poor wording on my part, rephrase: When I create a slackbuild for an app that has both 64-bit and 32-bit versions, is it required that I provide links to the 32-bit version in the .info file, and include the code to install it in the .SlackBuild? "Has both 64-bit and 32-bit versions" means the download site has separate downloads? In that case, yes, you should include both in the .info file, and the script should handle either (examine the ARCH variable as needed, etc). I don't know that I'd go so far as to say it's *required*, but it's polite at least. I ask because I have't run 32-bit for years and it's difficult to meaningfully test it. If you really want to test it, you could use VM software like qemu or virtualbox, install 32-bit Slackware in a virtual machine. If you don't have the time/energy/etc to do the testing, you might find someone on the mailing list who does run 32-bit, and is interested in using your application, who wouldn't mind testing it on 32-bit for you. Or, you might punt: in your README put something like "The author has not tested the 32-bit version of this software. Please send mail if you run into problems on 32-bit". Then be willing to work with whoever does send you mail about it (if it ever happens). ___ 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] 32-bit programs, required to maintain?
On 4/16/20, Andrew Payne wrote: > Poor wording on my part, rephrase: > > When I create a slackbuild for an app that has both 64-bit and 32-bit > versions, is it required that I provide links to the 32-bit version in the > .info file, and include the code to install it in the .SlackBuild? "Has both 64-bit and 32-bit versions" means the download site has separate downloads? In that case, yes, you should include both in the .info file, and the script should handle either (examine the ARCH variable as needed, etc). I don't know that I'd go so far as to say it's *required*, but it's polite at least. > I ask because I have't run 32-bit for years and it's difficult to > meaningfully test it. If you really want to test it, you could use VM software like qemu or virtualbox, install 32-bit Slackware in a virtual machine. If you don't have the time/energy/etc to do the testing, you might find someone on the mailing list who does run 32-bit, and is interested in using your application, who wouldn't mind testing it on 32-bit for you. Or, you might punt: in your README put something like "The author has not tested the 32-bit version of this software. Please send mail if you run into problems on 32-bit". Then be willing to work with whoever does send you mail about it (if it ever happens). ___ 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] 32-bit programs, required to maintain?
Poor wording on my part, rephrase: When I create a slackbuild for an app that has both 64-bit and 32-bit versions, is it required that I provide links to the 32-bit version in the .info file, and include the code to install it in the .SlackBuild? I ask because I have't run 32-bit for years and it's difficult to meaningfully test it. On Thu, 16 Apr 2020, Fernando Lopez wrote: it is autodetected... if you have a 32bit system it compiles a 32 bit one... if you have 64 bit... you get a 64 bit one... On Thu, Apr 16, 2020 at 10:13 AM Andrew Payne wrote: Is it expected of maintainers to provide 32-bit versions of software when they are available? Thanks, Andrew ___ 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/ -- Regards, Fernando Lopez Jr. ___ 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] 32-bit programs, required to maintain?
On 2020-04-16 12:12, Andrew Payne put forth the proposition: > Is it expected of maintainers to provide 32-bit versions of software when > they are available? > > Thanks, > Andrew Hi Andrew, It depends. Is it pre-compiled software? If so, and there are both separate 32 and 64 bit versions, then it's normal to include both versions if possible. You would use the options with the _x86_64 suffix in the .info for the 64 bit version, and plain DOWNLOAD and MD5SUM for the 32 bit. However, if only a 64 bit version is available, then in the .info file we would use DOWNLOAD="UNSUPPORTED" for 32 bit. Hope that helps. -- Dave The antibloat squad! For those interested in no bloat, minimal desktop Linux gopher://tty1.uk/1/?minimal-linux http://tty1.uk/minimal-linux #minimallinux @ chat.freenode.net signature.asc Description: PGP signature ___ 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] 32-bit programs, required to maintain?
i had assumed this type of thing would be fairly automatic. are you talking about something pre-compiled? (huge and difficult to build usually) -- Alexander Grotewohl https://dcclost.com From: SlackBuilds-users on behalf of Andrew Payne Sent: Thursday, April 16, 2020 12:12:42 PM To: slackbuilds-users@slackbuilds.org Subject: [Slackbuilds-users] 32-bit programs, required to maintain? Is it expected of maintainers to provide 32-bit versions of software when they are available? Thanks, Andrew ___ 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] 32-bit programs, required to maintain?
it is autodetected... if you have a 32bit system it compiles a 32 bit one... if you have 64 bit... you get a 64 bit one... On Thu, Apr 16, 2020 at 10:13 AM Andrew Payne wrote: > Is it expected of maintainers to provide 32-bit versions of software when > they are available? > > Thanks, > Andrew > ___ > 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/ > > -- Regards, Fernando Lopez Jr. ___ 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] 32-bit programs, required to maintain?
Is it expected of maintainers to provide 32-bit versions of software when they are available? Thanks, Andrew ___ 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] new coturn slackbuild
Thanks!
2 things I see in coturn.SlackBuild:
* You added the new maintainer correctly, but the others never
maintained/supported (the SB is based on another) it, so I can
delete these lines.
* You forgot to remove INSTALL file so it's fixed now. :D
Thank you again, I can submit it now.
Le 16/04/2020 à 08:06, Dave Woodfall a écrit :
On 2020-04-16 07:35,
Thomas Bourdon put forth the proposition:
Hi,
Thanks Dave! You said you fixed these issues but I can't find the SB fixed.
It doesn't matter, I also fixed exactly as you say, and I suggest 366 for
uid/gid.
I just wait to be sure 366 is a good choice, then I'll submit it.
Have a nice day!
I've attached it for you.
Le 15/04/2020 à 20:04, Dave Woodfall a écrit :
Hi Thomas,
I've found a few issues, but otherwise it's good:
The .info file:
We can't use variables in the .info file like this:
https://github.com/coturn/coturn/archive/${VERSION}/${PRGNAM}-${VERSION}.tar.gz
This one works:
DOWNLOAD="https://github.com/coturn/coturn/archive/4.5.1.1/coturn-4.5.1.1.tar.gz;
The SlackBuild:
I notice that you've used 900 for UID and GID, and we are only at 365
in https://slackbuilds.org/uid_gid.txt
It's best to ask for a UID and GID here or in IRC so we can keep
track of new numbers added in that list.
I've added a note above the copyright notice to say that it's now
maintained by you.
It's not usually necessary to out the INSTALL file with the documents
for /usr/doc (although I'm guilty of that too sometimes.)
README:
No need to put the homepage in the README, although it may go in the
slack-desc. I've also fixed a typo.
slack-desc:
The same typo here.
There shouldn't be any spaces after the : on blank lines. It's
useful if you have a way of checking for trailing whitespace in your
editor.
Those are the only issues I could see.
Cheers.
___
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/
--
Thomas Bourdon
___
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] new coturn slackbuild
On 2020-04-16 07:35,
Thomas Bourdon put forth the proposition:
> Hi,
>
> Thanks Dave! You said you fixed these issues but I can't find the SB fixed.
> It doesn't matter, I also fixed exactly as you say, and I suggest 366 for
> uid/gid.
>
> I just wait to be sure 366 is a good choice, then I'll submit it.
>
> Have a nice day!
I've attached it for you.
> Le 15/04/2020 à 20:04, Dave Woodfall a écrit :
> > Hi Thomas,
> >
> > I've found a few issues, but otherwise it's good:
> >
> >
> > The .info file:
> >
> > We can't use variables in the .info file like this:
> >
> > https://github.com/coturn/coturn/archive/${VERSION}/${PRGNAM}-${VERSION}.tar.gz
> >
> > This one works:
> >
> > DOWNLOAD="https://github.com/coturn/coturn/archive/4.5.1.1/coturn-4.5.1.1.tar.gz;
> >
> >
> > The SlackBuild:
> >
> > I notice that you've used 900 for UID and GID, and we are only at 365
> > in https://slackbuilds.org/uid_gid.txt
> >
> > It's best to ask for a UID and GID here or in IRC so we can keep
> > track of new numbers added in that list.
> >
> > I've added a note above the copyright notice to say that it's now
> > maintained by you.
> >
> > It's not usually necessary to out the INSTALL file with the documents
> > for /usr/doc (although I'm guilty of that too sometimes.)
> >
> >
> > README:
> >
> > No need to put the homepage in the README, although it may go in the
> > slack-desc. I've also fixed a typo.
> >
> > slack-desc:
> >
> > The same typo here.
> >
> > There shouldn't be any spaces after the : on blank lines. It's
> > useful if you have a way of checking for trailing whitespace in your
> > editor.
> >
> > Those are the only issues I could see.
> >
> > Cheers.
coturn.tar.gz
Description: GNU Zip compressed data
signature.asc
Description: PGP signature
___
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/
