Search Criteria
Package Details: task-spooler 1.0.3-4
Package Actions
Git Clone URL: | https://aur.archlinux.org/task-spooler.git (read-only, click to copy) |
---|---|
Package Base: | task-spooler |
Description: | Queue up tasks from the shell for batch execution |
Upstream URL: | https://viric.name/soft/ts/ |
Licenses: | GPL-2.0-or-later |
Submitter: | jneidel |
Maintainer: | jneidel (alub) |
Last Packager: | alub |
Votes: | 37 |
Popularity: | 0.007598 |
First Submitted: | 2023-05-28 18:05 (UTC) |
Last Updated: | 2024-07-22 19:52 (UTC) |
Latest Comments
1 2 3 4 5 6 Next › Last »
m040601 commented on 2024-07-22 23:25 (UTC) (edited on 2024-07-22 23:36 (UTC) by m040601)
@alub
Thanks for your work and commitment maintaining this PKGBUILD
You should add your name to that list.
No, no, no. This tool is definetely not obsolete.
This "task-spooler" is an extremely usefull and underrated simple little tool, used by many of us. It's just that it's original web page, http://viric.name/soft/ts/ is a bit messy and badly maintained.
Very small, an incredible 70KB,
The only other similar alternative are,
pueue, an official Arch package, also modern, very well maintained, but big (12MB) and written in Rust,
Another one is a fork of "task-spooler" on github, https://github.com/justanhduc/task-spooler also called "task-spooler".
There is also "nq" made by a very competent developer,
But I, personally, never ended up using it since task-spooler was enough for me.
alub commented on 2024-07-22 20:01 (UTC)
Hello, I’ve incorporated the requested changes, thanks for the suggestions!
An AUR user flagged this package as obsolete, I don’t have upstream notifications.
kseistrup commented on 2024-07-22 19:00 (UTC)
The
aarch64
architecture (e.g., RPi4) could also be relevant.Also, the license should be
GPL-2.0-or-later
, now that Arch has started using SPDX compæiant license identifiers.m040601 commented on 2024-07-22 18:57 (UTC)
Quoting the file "PORTABILITY"
That is true. It even has zero dependecies. I my self have been running task-spooler on Arch Linux Arm for years (Raspberry Pi 2b)
Could you please change,
To
Thanks in advance.
m040601 commented on 2024-07-22 18:48 (UTC) (edited on 2024-07-22 19:23 (UTC) by m040601)
$ wget https://viric.name/soft/ts/ts-1.0.3.tar.gz
$ tar tf ts-1.0.3.tar.gz
You already do this for "TRICKS",
Could you please make sure that at least the very useful "Changelog" also ends up in
Thanks in advance
PS: I am curious how you got notified of a new release available ?
I tried the page, https://viric.name/soft/ts/ and nothing works there. Not the mailing list, not the google groups not the web based source code viewer. The links are broken or only old messages in the mailing lists.
Even debian, https://packages.debian.org/search?keywords=task+spooler&searchon=names&suite=stable§ion=all , seems to be stuck in version 1.0.1 and have not noticed any updates to 1.0.3
jneidel commented on 2023-07-06 18:09 (UTC)
@m040601 & @kseistrup I've reverted to generic source, while keeping the arch as is. Thus communicating that it is an x86 package, but you may try to build it anyway:
https://aur.archlinux.org/cgit/aur.git/commit/?h=task-spooler&id=6973b2981fa1cf49ad061d309599a6aba026c04e
kseistrup commented on 2023-06-06 05:14 (UTC)
@m040601 The archcitecture field is meant to indicate which architecture the final package can run on: A
*-x86_64.pkg.tar.zst
can run only on the x86_64 platform, not on an ARM processor, and so on. A good example of an “any” package is a package containing a python module in pure python.Task spooler is a binary program that will run only on the platform for which is has been compiled, therefore “any” is the wrong choice. See
PKGBUILD(5)
for details.The reason why it failed before was because the maintainer had put
source_x86_64=(…)
inPKGBUILD
, where it should just have beensource=(…)
. When_x86_64
has been removed fromsource_x86_64
andsha256sums_x86_64
, people will be able to answerY
to the “Compile anyway?” question.It is, of course, also possible to create an array of all possible architectures.
m040601 commented on 2023-06-05 23:00 (UTC)
Task spooler works in "any" architecture.
If you dont want to put "any", just change it to
(ex, https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=yay)
kseistrup commented on 2023-06-05 15:39 (UTC) (edited on 2023-06-05 15:42 (UTC) by kseistrup)
@m040601
task-spooler
is not an “any” package, additional architectures have to be added explicitly.However, the
PKGBUILD
has e.g.source_x86_64=…
, something that should be justsource=…
.m040601 commented on 2023-06-05 15:33 (UTC) (edited on 2023-06-05 15:40 (UTC) by m040601)
Some adjustments are still needed after the recent merges in this PKGBUILD
I was trying to update "task-spooler" in my Archlinux systems. I'm using yay.
On my x86 system,
All seems OK, havent noticed any problem.
But, on my Archlinux ARM system (armv7h), where I have been using task-spooler for years,
I answered yes, as I have been doing for years, because "task-spooler" does work in multiple architectures. You can see in the Debian page that it is indeed available for x86, arm, mips, etc, https://packages.debian.org/bullseye/task-spooler
Then,
Hmmmm .... that line "...task-spooler/PKGBUILD: line 19: cd: ts-1.0.2: No such file or directory" is really strange. What is that "ts" still doing there ?. Tried a clean build, same problem.
So anyway, this PKGBUILD needs a change in
to something like
1 2 3 4 5 6 Next › Last »