[Slackbuilds-users] Creating First Slackbuilds and Github
Hi, I'm new to creating SlackBuilds and using github so I apologize if this is obvious. I'm in the process of putting my first SlackBuilds together. The repos are on github. The first repo has archived releases but I would like to use master up to the most recent commit. And the second repo only has a master and no archived releases. I'm curious what the policy is regarding slackbuilds.org hosting tarballs? 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] Updates - 20220317.1
Hi Qun-Ying, actually stuff in /extra, not being part of a Slackware full installation, is provided also here if being a dependency of something else: this is the case, for example, for fltk or the various java implementations... Matteo Il giorno ven 18 mar 2022 alle ore 20:21 Qun-Ying ha scritto: > Hi, > > fltk is provided from extra in official release, should be removed > from SlackBuild. > ___ 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] Updates - 20220317.1
Hi, fltk is provided from extra in official release, should be removed from SlackBuild. On 3/17/22, Willy Sudiarto Raharjo wrote: > Hey guys, > > For the last few days we have been making a lot of changes (almost 1.5k > commits in this batch of update alone) consists of fixing build failures > on x86 (still ongoing process), renaming for python scripts, and fixing > READMEs. Make sure not to break the READMEs again in the future. > > Just another reminder that submission form is NOT YET opened and new > scripts should go via submission form and not submitted via github/gitlab. > > > Thu Mar 17 17:28:01 UTC 2022 > academic/bowtie2: Mark x86 as unsupported. > academic/bowtie: Mark x86 as unsupported. > academic/celestia: Wrap README at 72 columns. > academic/ds9: Wrap README at 72 columns. > academic/fiji: Fix 32bit build. > academic/fiji: Fix source name on 32bit. > academic/gcompris-qt: Updated for version 2.3.1. > academic/labplot2: Wrap README at 72 columns. > academic/ladr: Wrap README at 72 columns. > academic/ncbi-blast+: Fix build on i586. > academic/octave: Wrap README at 72 columns. > academic/qrupdate: Wrap README at 72 columns. > academic/root: Actually install doinst.sh. > academic/scipy3: Wrap README at 72 columns. > academic/spqr: Wrap README at 72 columns. > academic/suitesparse: Wrap README at 72 columns. > academic/treebest-ensembl: Wrap README at 72 columns. > academic/ugene: Wrap README at 72 columns. > academic/umfpack: Wrap README at 72 columns. > academic/verilator: Make slack-desc ASCII. > academic/xflr5: Wrap README at 72 columns. > accessibility/eflite: Wrap README at 72 columns. > audio/TiMidity++: Handle content-disposition download. > audio/amSynth: Wrap README at 72 columns. > audio/clementine: Wrap README at 72 columns. > audio/clockchimes: Wrap README at 72 columns. > audio/cmus: Wrap README at 72 columns. > audio/darkice: Wrap README at 72 columns. > audio/deadbeef: Wrap README at 72 columns. > audio/gnump3d: Wrap README at 72 columns. > audio/google-musicmanager: Fix broken symlink. > audio/jack_capture: Wrap README at 72 columns. > audio/rhythmbox: Wrap README at 72 columns. > audio/tta: Fix 32-bit build. > desktop/Qogir-icon-theme: Fix VERSION in script. > desktop/Surfn: Fix VERSION in script. > desktop/bumblebee-status: Wrap README at 72 columns. > desktop/e16: Remove template comment. > desktop/obshutdown: Fix DOWNLOAD/HOMEPAGE. > desktop/xdm-slackware-theme: Wrap README at 72 columns. > development/J-Link: Wrap README at 72 columns. > development/android-tools: Add network warning to README. > development/apache-maven: Updated for version 3.8.5. > development/bluefish: Wrap README at 72 columns. > development/dfu-programmer: Move setup instructions to README.SBo. > development/f2c: Remove template comment. > development/gcc5: Fix sbolint nitpicks. > development/git-extras: Wrap README at 72 columns. > development/github-cli: Updated for version 2.6.0 > development/golang-googlecode-gotools: Wrap README at 72 columns. > development/hugo: Updated for version 94.2. > development/jdk11: Wrap README at 72 columns. > development/jupyter-nbclient: Update for 0.5.13 > development/jupyter-nbconvert: Update for 6.4.3 > development/jupyterlab_pygments: Wrap README at 72 columns. > development/lighttable: Add network warning to README. > development/mysql-workbench: Wrap README at 72 columns. > development/nodejs: Updated for version 17.7.1. > development/openjdk7: Move template preamble to top of script. > development/php-xdebug: Fix PRGNAM in script. > development/racer: Add network warning to README. > development/racer: Wrap README at 72 columns. > development/sbcl: Updated for version 2.2.2 > development/shc: Fix DOWNLOAD. > development/shc: Wrap README at 72 columns. > development/shiboken2: Wrap README at 72 columns. > development/sqlcl: Wrap README at 72 columns. > development/sqlitebrowser: Wrap README at 72 columns. > development/tora: Fix VERSION in script. > development/vscode-bin: Updated for version 3.6.1. > games/clksignal-roms: Host 2 of the downloads under sane names. > games/dmagnetic: gzip the man pages. > games/jin: Update email > games/lutris: Updated for version 0.5.9.1, new maintainer > games/m64py: Remove template comment. > games/scid_vs_pc: Wrap README at 72 columns. > games/scummvm: Wrap README at 72 columns. > games/sl: Wrap README at 72 columns. > games/smashbattle: Wrap README at 72 columns. > games/solarus-quest-editor: Wrap README at 72 columns. > games/speed-dreams: Wrap README at 72 columns. > games/steam: Wrap README at 72 columns. > games/tintin: Wrap README at 72 columns. > games/tome-ah: Wrap README at 72 columns. > games/trigger-rally: Wrap README at 72 columns. > games/tuxnes: Wrap README at 72 columns. > games/uligo: Wrap README at 72 columns. > games/ut2004: Wrap README at 72 columns. > games/vcmi: updated for version 0.99_git20220314 > games/voxelands: Wrap README at 72 columns. > games/warzone2100: Wrap README at 72 columns. >
Re: [Slackbuilds-users] peer-to-peer: aMule / mldonkey , gnutella, soulseek, transmission-qt, etc.?
W dniu 18.03.2022 o 04:37, David Chmelik pisze: It's good EiskaltDC++ and SoulSeek are still on but latter's six years old but for some idiotic reason they made newer version require SELinux. Hi David, I'm the maintainer of SoulseekQt. There is a workaround for this SELinux dependency, I just didn't have the motivation to implement it and post an update to SBo. But I can look into this if there's demand for it. I recommend Nicotine+ over the official client anyway. :) Regards, Dominik ___ 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] Surprising failure building GHC
--- Original Message --- On Thursday, March 17th, 2022 at 10:21 PM, Luveh Keraph <1.41...@gmail.com> wrote: > After getting Sage out of the way, and installing Sphinx for good measure, > ghc still refuses to build: Try installing without Sphinx. On my build I did not have Sphinx installed and it worked. Erich ___ 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] Nextcloud client
I keep a current build of it, so I'd be willing to take over maintenance if no one objects. May i ask to send the build to me or this list? 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/