Re: [Slackbuilds-users] suggestion for a new category for fonts
"B. Watson" writes: > On Thu, 21 Mar 2024, Willy Sudiarto Raharjo wrote: > >> Since we have search form in our website, i wonder how many people would go >> through each categories when looking for some scripts instead of just using >> the >> search form? > > OK, so in that case, why do we have categories at all? Would it bother > you to get rid of them entirely? Other than the amount of work it > would take to accomplish it, I mean. Would we be better off if there > had never been categories? > > We could just add a keyword for each build, with its former category. > system/dosbox would just become dosbox/, and get "system" added to its > list of keywords... > > ...which is silly of course. It's intended to be silly. > ___ > 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/ I do use categories often. I am finding them useful when understanding optional deps, and when searching for "related software". Admittedly, perhaps not _all_ of them are useful, but for me many make sense. I am often finding myself searching for packages using sbopkg -g. They are not fool-proof, but they do help when there are packages with similar names, but doing different things. For example, I might be searching for something which encrypts with aes: sbopkg -g aes. This is the result: academic/aeskulap 0.2.2_e710562d haskell/haskell-aeson 2.0.2.0 haskell/haskell-aeson-compat 0.3.10 haskell/haskell-aeson-pretty 0.8.9 haskell/haskell-cipher-aes0.2.11 haskell/haskell-hslua-aeson 2.1.0 libraries/SlowAES 0.1a1 libraries/libcaes 20230406 office/unaesgcm 0.4.1.20220827_0cf9cb perl/perl-Crypt-OpenSSL-AES 0.02 python/pyaes 1.6.1 system/aespipe2.4g From those I immediately see that I need no "academic, haskell, libraries, perl, python." Which leaves me with either unaesgcm or aespipe. And both of those generally do what I expect them to do. When a program is in the "network" category, very high chances are that it doesn't work without network access. Some things are not entirely clear, such as "desktop/office/development". Like, I am a developer, and I use a desktop computer, and I work in an office. But even so, a "desktop" program probably has a GUI, or at least and interactive TUI. Replacing categories _entirely_ with tags might be an option, but for me it seems too radical of a reform, to be honest. But at least (python, ruby, haskell), "network", and "libraries" do make a lot of sense. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) 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] suggestion for a new category for fonts
It is good to have suggestion, but then all decision is by the slackbuild admin. For the use case, I occasionally browser through the categories not looking for a particular package but to discover what packages are available for Slackware and sometimes found some packages that I would want to try on. It would be nice if the categories are more accurate. On Wed, Mar 20, 2024 at 8:00 PM Willy Sudiarto Raharjo wrote: > > > Currently fonts are put under category system, they mix with other > > system tools. Would it be better to have a separate category (fonts) > > for them? > > This is my personal opinion and do not express other admin's opinion > > i think having more categories doesn't really give benefits to this > project besides cosmetic values. It just adds more work moving scripts > around during development cycle, adding new categories in the database, > web forms, etc. > > Since we have search form in our website, i wonder how many people would > go through each categories when looking for some scripts instead of just > using the search form? ___ 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] suggestion for a new category for fonts
On Thu, 21 Mar 2024, Willy Sudiarto Raharjo wrote: Since we have search form in our website, i wonder how many people would go through each categories when looking for some scripts instead of just using the search form? OK, so in that case, why do we have categories at all? Would it bother you to get rid of them entirely? Other than the amount of work it would take to accomplish it, I mean. Would we be better off if there had never been categories? We could just add a keyword for each build, with its former category. system/dosbox would just become dosbox/, and get "system" added to its list of keywords... ...which is silly of course. It's intended to be silly. ___ 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] suggestion for a new category for fonts
On 3/19/24 11:31 AM, Qun-Ying wrote: [...] Currently fonts are put under category system, they mix with other system tools. Would it be better to have a separate category (fonts) for them? yes ___ 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] suggestion for a new category for fonts
Currently fonts are put under category system, they mix with other system tools. Would it be better to have a separate category (fonts) for them? This is my personal opinion and do not express other admin's opinion i think having more categories doesn't really give benefits to this project besides cosmetic values. It just adds more work moving scripts around during development cycle, adding new categories in the database, web forms, etc. Since we have search form in our website, i wonder how many people would go through each categories when looking for some scripts instead of just using the search form? During development cycle (which usually started when Pat declared Alpha or Beta version of Slackware-Current), admins will be busy verifying each scripts in the repo to make sure it builds fine against slackware-current, which will be a moving target since Pat usually have a long period of testing before he declares stable release. Some of these scripts have been checked and fixed by Ponce so it gives a headstart for us, but we have over 9k scripts (per December 2023) and it's growing each week. There are tons of work to make sure the new repo is ready when next Slackware is released and we are targeting for same-day release (if it's possible). -- Willy Sudiarto Raharjo ___ 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] jq fails to build
On Wed, 20 Mar 2024, nnb via SlackBuilds-users wrote: Some tests fail because of locale setting. I did run sbopkg like this and the build worked fine 'LANG=C sbopkg'. Hopefully the maintainer can add 'export LANG=C' somewhere near the top of the script. ___ 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] suggestion for a new category for fonts
slackware-specific On Wed, Mar 20, 2024 at 12:27:45PM +0100, j+sbo-us...@maschinengott.de wrote: > On 20.03.24 07:32, Lockywolf wrote:> > > +1 for fonts as its own category, and, if possible, please, one more > > category for "slackware-specific" stuffs, such as: > > As a few people have spoken in favour of this, what would be a good name? > Just to get the conversation going: I think "slackware" is too unspecific. > My first thought was "meta", but I think it does not fit all the proposed > packages. Same with "packaging". > ___ > 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] kicad md5sum mismatch (again)
this is a known issue. On Wed, Mar 20, 2024, 2:54 PM wrote: > hey, for KiCad 8.0 > > Expected: dd187abbfb1109f8d417aa08fc75d19f > Found:03f46e27af35c003c985f96618d566a9 > ___ > 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] suggestion for a new category for fonts
On Wed, Mar 20, 2024 at 5:44 AM Luc Van Rompaey wrote: > > "slack-tools" or some such? > > > j+sbo-us...@maschinengott.de schreef op 20 maart 2024 12:27:45 CET: +1 for "slack-tools" ___ 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] jq fails to build
build failed for me too, in my case it was this issue: https://github.com/jqlang/jq/issues/3038 Some tests fail because of locale setting. I did run sbopkg like this and the build worked fine 'LANG=C sbopkg'. Thank you, that worked ! -- Regards, Tonus ___ 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] jq fails to build
Hello, Am 20.03.24 um 18:50 schrieb Tonus: Hi list, Just tried to update jq and build failed on tests. [...] build failed for me too, in my case it was this issue: https://github.com/jqlang/jq/issues/3038 Some tests fail because of locale setting. I did run sbopkg like this and the build worked fine 'LANG=C sbopkg'. Best regards ___ 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] kicad md5sum mismatch (again)
hey, for KiCad 8.0 Expected: dd187abbfb1109f8d417aa08fc75d19f Found:03f46e27af35c003c985f96618d566a9 ___ 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] jq fails to build
Il giorno mer 20 mar 2024 alle ore 18:50 Tonus ha scritto: > │ PASS: tests/mantest > │ FAIL: tests/jqtest > │ PASS: tests/shtest > │ PASS: tests/utf8test > │ PASS: tests/base64test > │ FAIL: tests/optionaltest > │ PASS: tests/onigtest > │ PASS: tests/manonigtest > │ > == > │ Testsuite summary for jq 1.7.1 > │ > == > │ # TOTAL: 8 > │ # PASS: 6 > │ # SKIP: 0 > │ # XFAIL: 0 > │ # FAIL: 2 > │ # XPASS: 0 > │ # ERROR: 0 > hi Tonus, jq seems to build fine here so I am inclined to think about a local issue: for hints maybe you can have a look in your /tmp/SBo/jq-1.7.1/tests directory, and in particular check the content of the jqtest.log and optionaltest.log diles that you can find there... Matteo ___ 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] WIP: protobuf3 25.3
On Mon, Mar 11, 2024 at 09:13:58AM -0300, Slackbuilds Mailing List wrote:
I'm still looking for some guidelines on how developers usually create virtual
machines to test. I used virtualbox when I developed for debian, but I don't
like this approach anymore. I'm trying to learn LCX, and for slackware it
doesn't have templates ready to go, so there is that.
Hi
Not really a developer here but found great advice from Alien Bob with
qemu.
Can't find the source with a quick search so here's the pitch :
- create a qemu base image with genuine and up-to-date Slackware
- I only add autocompletion, bash magic key and sbo tools and tree
- then I use the following script to get a snapshot
- I launch it , do stuff and tests, save the package on host
- test on my machine and share on SBo
- an important thing is to get a share between machines
- another one is to keep a consistant SBo tree on base qemu image
Now the script from AlienBOB (modified but can't recall if/how) :
│ #!/bin/sh
│ #
│ # Start Slackware in QEMU
│ # Use QEMU snapshots (COW - Copy On Write images) for the purpose of
│ # testing software in a clean environment.
│
│ ## ---
│ ## Create an empty 15GB image file like this:
│ ## # dd if=/dev/zero of=slackware.img bs=1k count=1500
│ ##
│ ## You must install a version of Slackware in this image file.
│ ## This installation will be your base image. It will not change unless
│ ## you want to install security patches.
│ ##
│ ## Then create the QCOW (qemu copy-on-write) file like this:
│ ## $ qemu-img create -b slackware.img -f qcow slackware_snapshot.qcow
│ ##
│ ## DO NOT commit the changes made in the QCOW file back to the base image!
│ ## The QCOW image is only used once and re-created every time the script
runs!
│ ##
---
│
│ # Location of your QEMU images:
│ IMAGEDIR=/path/to/disk_img/slackware
│
│ # ISO location
│
iso_file=/path/to/disk_img/slackware64-current-iso/slackware64-15.0-install-dvd.iso
│ # add next option to have it
│ # -cdrom "${iso_file}"
│
│ #[ ! -z $* ] && PARAMS=$*
│ # add command line parameters to defaults
│ PARAMS=$*
│
│ # Qemu can use SDL sound instead of the default OSS
│ export QEMU_AUDIO_DRV=sdl
│
│ # Whereas SDL can play through alsa:
│ export SDL_AUDIODRIVER=alsa
│
│ cd $IMAGEDIR
│ # Remove old QCOW file, create a new one:
│ if [ -f slackware-15.0_snapshot.qcow ]; then
│ rm -f slackware-15.0_snapshot.qcow
│ fi
│ qemu-img create -f qcow2 -b slackware64-15.0.qcow2 -F qcow2
slackware64-15.0_snapshot.qcow
│
│ qemu-system-x86_64 -enable-kvm -smp cpus=2 -smp maxcpus=3 -m 4096 -k fr -daemonize \
│ -vga virtio -boot menu=on -usb -drive file=slackware64-15.0_snapshot.qcow \
│ -fsdev local,id=repos,path=/path/to/share,security_model=none \
│ -device virtio-9p-pci,fsdev=repos,mount_tag=repos ${PARAMS}
>slackware-15.0_snapshot.log \
│ 2>slackware-15.0_snapshot.err
--
Regards,
Tonus
___
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] jq fails to build
Hi list, Just tried to update jq and build failed on tests. │ configure: WARNING: valgrind is required to test jq. │ checking for memmem... yes │ checking for sys/cygwin.h... no │ checking for shlwapi.h... no │ checking for pipenv... no │ checking for Python dependencies... no │ configure: WARNING: Error checking python dependencies: │ * │ * Python dependencies for building jq documentation not found. * │ * You can still build, install and hack on jq, but the manpage * │ * will not be rebuilt and new manpage tests will not be run. * │ * See docs/README.md for how to install the docs dependencies. * │ * and further │ PASS: tests/mantest │ FAIL: tests/jqtest │ PASS: tests/shtest │ PASS: tests/utf8test │ PASS: tests/base64test │ FAIL: tests/optionaltest │ PASS: tests/onigtest │ PASS: tests/manonigtest │ == │ Testsuite summary for jq 1.7.1 │ == │ # TOTAL: 8 │ # PASS: 6 │ # SKIP: 0 │ # XFAIL: 0 │ # FAIL: 2 │ # XPASS: 0 │ # ERROR: 0 │ == │ See ./test-suite.log │ Please report to https://github.com/jqlang/jq/issues │ == Installing valgrind gives same errors. -- Regards, Tonus ___ 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] suggestion for a new category for fonts
"slack-tools" or some such? j+sbo-us...@maschinengott.de schreef op 20 maart 2024 12:27:45 CET: >On 20.03.24 07:32, Lockywolf wrote:> >> +1 for fonts as its own category, and, if possible, please, one more >> category for "slackware-specific" stuffs, such as: > >As a few people have spoken in favour of this, what would be a good name? Just >to get the conversation going: I think "slackware" is too unspecific. My first >thought was "meta", but I think it does not fit all the proposed packages. >Same with "packaging". >___ >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] suggestion for a new category for fonts
On 3/19/24 11:32 PM, Lockywolf wrote: [...] +1 for fonts as its own category, and, if possible, please, one more category for "slackware-specific" stuffs, such as: 1. slackrepo 2. slackrepo-hints 3. sbotools 4. sbo-create 5. sbo-maintainer-tools 6. sbotools 7. sboui 8. slpkg 9. listpkg 10. gnome-pkgtool 11. findpkg 12. slack-osquery 13. slack-utils 14. slackchlog 15. slackroll 16. slackupdr 17. slackware-grub2-theme 18. slackyd 19. slack-wallpapers 20. slackware-xdg-menu 21. slackware-xdm-theme 22. xdm-slackware-theme 23. fortune-slackware 24. perl-CPANPLUS-Dist-Slackware 25. python2-slacklog These are many mixed categories and are best where they are now. I mentioned maybe 10+ more but in fact there are dozens/hundreds, as software from all categories is patched for Slackware. I don't want command-line system tools, package management tools mixed up in a category with GUI stuff and development dependencies for other stuff I don't even use. ___ 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] Linphone maintenance
On 20/03/2024 01:03, B. Watson wrote: On Wed, 20 Mar 2024, Sebastian Arcus wrote: I have copied Euan into the email I sent to the list on 07 Feb 2024 asking if the Linphone scripts could be updated - but there hasn't been any reply. I already accepted to look after BcToolbox, which he used to maintain - as he hasn't been active in a long time. Should I try to contact Euan again? Don't bother. Euan Thoms' last activity was in November of 2017, over 6 years ago. I think we can consider this one an ex-maintainer. Whoever wants to take over linphone, and any other of his builds, just submit an update (possibly after discussing it on this mailing list). I recommend whoever takes linphone also takes its dependencies that were maintained by Euan: libraries/libantlr3c libraries/libsrtp libraries/bzrtp libraries/belle-sip Whoever wants them should also take Euan's other builds: libraries/ccrtp libraries/libzrtpcpp libraries/msx264 libraries/ucommon network/netdrive-connector That would make sense. They are quite a few packages, and I have no idea how straight forward will be to bring them up to date, but if nobody else is stepping up, I can try to push updates for the above, as and when I find the time. It could be a few weeks until I get to it - if that's ok. I do use Linphone from time to time, so I would prefer it stays in the SBo repo. ___ 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] suggestion for a new category for fonts
On 20.03.24 07:32, Lockywolf wrote:> > +1 for fonts as its own category, and, if possible, please, one more > category for "slackware-specific" stuffs, such as: As a few people have spoken in favour of this, what would be a good name? Just to get the conversation going: I think "slackware" is too unspecific. My first thought was "meta", but I think it does not fit all the proposed packages. Same with "packaging". ___ 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] suggestion for a new category for fonts
Hi list That would be great for the 2 proposals. Regards -- Tonus Le 20 mars 2024 08:32:29 GMT+01:00, David Chmelik a écrit : >On 3/19/24 11:32 PM, Lockywolf wrote: >> KB_SBo writes: >> On 3/19/24 11:31, Qun-Ying wrote: [...] Currently fonts are put under category system, they mix with other system tools. Would it be better to have a separate category (fonts) for them? >>> +1 for fonts as its own category >>> >>> -kb [...] >> +1 for fonts as its own category, and, if possible, please, one more >> category for "slackware-specific" stuffs, such as: >> >> 1. slackrepo >> 2. slackrepo-hints >> 3. sbotools >> 4. sbo-create >> 5. sbo-maintainer-tools >> 6. sbotools >> 7. sboui >> 8. slpkg >> 9. listpkg >> 10. gnome-pkgtool >> 11. findpkg >> 12. slack-osquery >> 13. slack-utils >> 14. slackchlog >> 15. slackroll >> 16. slackupdr >> 17. slackware-grub2-theme >> 18. slackyd >> 19. slack-wallpapers >> 20. slackware-xdg-menu >> 21. slackware-xdm-theme >> 22. xdm-slackware-theme >> 23. fortune-slackware >> 24. perl-CPANPLUS-Dist-Slackware >> 25. python2-slacklog >> >> This is comparable to the size of, say accessibility/ >> >> nowadays those packages are scattered over many categories, not just >> system/, and system/ has a lot of packages, whereas having all >> Slackware-related in one place would have been really convenient. > >There are several/many others, also, like depfinder, gslapt, hoorex, magiic, >slapt-get, slapt-src, slpkg, sourcery, spi, spkg... not all have the word >'slack' in. >___ >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] suggestion for a new category for fonts
I'd be in favor of both new categories. ___ 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] suggestion for a new category for fonts
On 3/19/24 11:32 PM, Lockywolf wrote: KB_SBo writes: On 3/19/24 11:31, Qun-Ying wrote: [...] Currently fonts are put under category system, they mix with other system tools. Would it be better to have a separate category (fonts) for them? +1 for fonts as its own category -kb [...] +1 for fonts as its own category, and, if possible, please, one more category for "slackware-specific" stuffs, such as: 1. slackrepo 2. slackrepo-hints 3. sbotools 4. sbo-create 5. sbo-maintainer-tools 6. sbotools 7. sboui 8. slpkg 9. listpkg 10. gnome-pkgtool 11. findpkg 12. slack-osquery 13. slack-utils 14. slackchlog 15. slackroll 16. slackupdr 17. slackware-grub2-theme 18. slackyd 19. slack-wallpapers 20. slackware-xdg-menu 21. slackware-xdm-theme 22. xdm-slackware-theme 23. fortune-slackware 24. perl-CPANPLUS-Dist-Slackware 25. python2-slacklog This is comparable to the size of, say accessibility/ nowadays those packages are scattered over many categories, not just system/, and system/ has a lot of packages, whereas having all Slackware-related in one place would have been really convenient. There are several/many others, also, like depfinder, gslapt, hoorex, magiic, slapt-get, slapt-src, slpkg, sourcery, spi, spkg... not all have the word 'slack' in. ___ 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] suggestion for a new category for fonts
Il 19/03/24 19:31, Qun-Ying ha scritto: Hi, Currently fonts are put under category system, they mix with other system tools. Would it be better to have a separate category (fonts) for them? It seems a good idea -- * Giancarlo Dessì https://www.giand.it https://github.com/giandex Slackware Linux... because it works! * ___ 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] suggestion for a new category for fonts
+1 On Wed, Mar 20, 2024, 1:41 AM Lockywolf < for_slackbuilds-users_mlist_2023-04...@lockywolf.net> wrote: > > > > KB_SBo writes: > > > On 3/19/24 11:31, Qun-Ying wrote: > >> Hi, > >> > >> Currently fonts are put under category system, they mix with other > >> system tools. Would it be better to have a separate category (fonts) > >> for them? > >> > >> > > > > +1 for fonts as its own category > > > > -kb > > > > > > > > ___ > > 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/ > > +1 for fonts as its own category, and, if possible, please, one more > category for "slackware-specific" stuffs, such as: > > 1. slackrepo > 2. slackrepo-hints > 3. sbotools > 4. sbo-create > 5. sbo-maintainer-tools > 6. sbotools > 7. sboui > 8. slpkg > 9. listpkg > 10. gnome-pkgtool > 11. findpkg > 12. slack-osquery > 13. slack-utils > 14. slackchlog > 15. slackroll > 16. slackupdr > 17. slackware-grub2-theme > 18. slackyd > 19. slack-wallpapers > 20. slackware-xdg-menu > 21. slackware-xdm-theme > 22. xdm-slackware-theme > 23. fortune-slackware > 24. perl-CPANPLUS-Dist-Slackware > 25. python2-slacklog > > This is comparable to the size of, say accessibility/ > > nowadays those packages are scattered over many categories, not just > system/, and system/ has a lot of packages, whereas having all > Slackware-related in one place would have been really convenient. > > > -- > Your sincerely, > Vladimir Nikishkin (MiEr, lockywolf) > (Laptop) > ___ > 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] suggestion for a new category for fonts
KB_SBo writes: > On 3/19/24 11:31, Qun-Ying wrote: >> Hi, >> >> Currently fonts are put under category system, they mix with other >> system tools. Would it be better to have a separate category (fonts) >> for them? >> >> > > +1 for fonts as its own category > > -kb > > > > ___ > 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/ +1 for fonts as its own category, and, if possible, please, one more category for "slackware-specific" stuffs, such as: 1. slackrepo 2. slackrepo-hints 3. sbotools 4. sbo-create 5. sbo-maintainer-tools 6. sbotools 7. sboui 8. slpkg 9. listpkg 10. gnome-pkgtool 11. findpkg 12. slack-osquery 13. slack-utils 14. slackchlog 15. slackroll 16. slackupdr 17. slackware-grub2-theme 18. slackyd 19. slack-wallpapers 20. slackware-xdg-menu 21. slackware-xdm-theme 22. xdm-slackware-theme 23. fortune-slackware 24. perl-CPANPLUS-Dist-Slackware 25. python2-slacklog This is comparable to the size of, say accessibility/ nowadays those packages are scattered over many categories, not just system/, and system/ has a lot of packages, whereas having all Slackware-related in one place would have been really convenient. -- Your sincerely, Vladimir Nikishkin (MiEr, lockywolf) (Laptop) 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/
