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.002238 |
First Submitted: | 2023-05-28 18:05 (UTC) |
Last Updated: | 2024-07-22 19:52 (UTC) |
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 Next › Last »
alub commented on 2023-03-27 22:19 (UTC)
@flylightning Thanks for reporting the issue, I fixed the patch.
flylightning commented on 2023-03-27 22:10 (UTC)
build fail:
make: *** No rule to make target 'ts', needed by 'install'. Stop.
I guess it is due to
ts-to-tsp.patch
changed the target binary name fromts
totsp
, maybe we should switch back to the old way of not changing Makefile and rename ts to tsp bymv
intead.alub commented on 2023-03-23 15:28 (UTC) (edited on 2023-03-24 21:14 (UTC) by alub)
Sorry for not replying, my AUR notifications were disabled for some reason.
@m040601 You’re right about package duplication, I’m not sure why that is originally.
I don’t get the remark about renaming ts to tsp: this is done in this package since 2017 according to the Git history.
As for the deletion request:
it was indeed out of date, I’ve done the update since I have notifications again, thanks for the head up
the PKGBUILD was not touched since 2021 simply because ts 1.0.1 was released in 2021
indeed, see above
the other package may be more active, but it didn’t change the man page to update the executable name until 2023-03-24 (which is why I used the Debian sources in the first place)
willemw commented on 2023-03-18 05:41 (UTC) (edited on 2023-03-18 05:52 (UTC) by willemw)
There tools mentioned all work a bit differently, so it may depend what you want to do.
flock
is probably already installed. Seeman flock
for usage examples: for use inside your own script and for around another script/program.kseistrup commented on 2023-03-17 21:21 (UTC)
@m040601 flock is owned by util-linux. However, flock (file lock) is just a tool to serialize jobs, it doesn't save the output or any of the other things task-spooler can do.
m040601 commented on 2023-03-17 21:14 (UTC)
Didnt know about this. What is this 'flock' ? Searched the AUR but couldn find anything.
willemw commented on 2023-02-22 19:25 (UTC)
'flock' is another great alternative.
willemw commented on 2023-02-22 19:20 (UTC)
Switching back from the Debian source to the upstream source again. Debian's version has been "out-of-date" for a long time. Hopefully the upstream "download availability" has improved and is maybe now more stable.
willemw commented on 2022-10-13 11:04 (UTC)
@m040601: some alternatives: 'at' (as you mentioned), Bash's 'disown' ('nohup'), 'tmux' (if you want to see the output directly in a tmux window pane) and systemd:
m040601 commented on 2022-09-25 23:08 (UTC) (edited on 2022-09-26 00:13 (UTC) by m040601)
Thanks for maintaining and caring about this PKGBUILD. An old and very usefull and underrated tool.
I'm not a developer, nor an AUR expert. Just and end user for whom this kind of tools is vital. Still comparing it and evaluating against "classical at/batch", "pueue", "nq" and others. Pitty we dont have a more thorought documentation and use cases (done by experts) in the Archwiki.
By the way, could any one point me to "quality" tutorials on the Internet about these kind of tools ? Maybe some book ?
More than the technical details, I'm interested in what use, and real world case scenarios, is there for this kind of tools in 2022. Cool and interesting uses for heavy cli command line users. From a home user perspective. Not from an IT business perspective.
I googled for weeks/months. But I'm having meager results. I suspect because this is a niche use cases. Not reddit posts. Not stackexchange "you could use .." posts. Not stuff from 1999. Not "fake" linux pseudo tutorial-listicles. The most "arch way" non bloated setup as possible.
I picked up a few use cases here and there as a helper tool for scheduled downloads with wget for example (in newsboat or youtube-dlp etc). But I'm sure there's much more. Just super curious how other archers are using it. In this age of "bloat" and "dockerisms" and "kubernetisms"
Now, backed to the issue, raised in the previous comments.
Since I'm not a programmer, neither a PKGBUILD expert, I dont have an opinion on which version should this "task-spooler" PKGBUILD follow. These are just my 2 cents.
First I was confused and spent a lot of time just to understand why the source is Debian and not the original https://viric.name/soft/ts/
Then I too ended up here after discovering the "justanhduc" version, https://github.com/justanhduc/task-spooler
I certainly dont want it to mess or clash with Arch Official packages. This, "task-spooler" does it the right way. Kudos, and big thank you for the attention to detail.
I just want it to be stable, without surprises, and usable for many years. I need it for scripts. I dont want this kind of tools to be constantly changing their API/modus operandi.
I just want it's "Description" in the AUR, patches applied, it's source URL's to be crystall clear and not confusing. Why save a few bytes and not type one or two more words ?
I just want it's PKGBUILD to include as many readmes/docs/example-files/ etc. I hate having to go back online to the Internet, just to learn how to use it.
One thing I didnt like in ,https://github.com/justanhduc/task-spooler, was the messy README. He just copied the original README and addded the word "originally by Luis ...". So fucking confusing. Is this the "original" README ? Was it edited ? He could have added clearly added one or two sentences, "this is a fork of XYZ ... " , "The difference is foobar ..."
It just irritates me as and end user, wasting so much time trying to figure out, when typing one or two sentences more would have done it
He doesnt explain his plans for the future, what is goals are. He does link to a blog post, https://www.justanhduc.tech/2021/02/03/Task-Spooler.html
But was last updated more than one year ago. It talks about "CPU only" this and "neural networks" that. What is relevant should be in a crystal clear updated and maintained README in the github.
So maybe first asking him to polish the README a little more, and talk about his plans for the future ?
Or even better, talk to Debian. Ask them their opinion. And coordinate with them ?
Exactly.
So that we, Archlinux, dont end up alone, by following one guy that might fail in the future ? So that we could have all the "eyes" looking at the same place ?
I'm not a Debian user, but I like it when AUR PKGBUILD's follow or at least keep an eye on how's Debian doing it. Especially for these kind of old tools. So that if I read a more popular tutorial for the masses on the Internet, I know it applies both to Arch and DEbian.
PS: As this wasnt enough, there is still another PKGBUILD "ts" living in the AUR, doing the same thing as "task-spooler", =https://aur.archlinux.org/packages/ts.
« First ‹ Previous 1 2 3 4 5 6 Next › Last »