mirror of
https://github.com/Glitchy-Sheep/boosty-downloader.git
synced 2026-10-14 21:33:23 +00:00
[GH-ISSUE #44] Project license? #1
Labels
No labels
api-drift
bug
ci
documentation
enhancement
enhancement
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Glitchy-Sheep/boosty-downloader#1
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @KorespondentAda on GitHub (Jul 26, 2025).
Original GitHub issue: https://github.com/Glitchy-Sheep/boosty-downloader/issues/44
On the botom of README.md there is noted that project licensed under MIT with link to
LICENSEfile that I cannot find in present or any other commit in git history.As I know, "MIT license" itself is ambiguous and license text should be provided.
I see no major problem with it, but I wanted to package your useful tool at AUR, and there is a good reasons to provide project license accurately, so I want to do so.
Of course if you doesn't mind packaging at all.
@Glitchy-Sheep commented on GitHub (Jul 27, 2025):
Oh, I don't mind at all - I'll attach the license soon. 👍
Just forgot about it. Thanks!
@KorespondentAda commented on GitHub (Aug 3, 2025):
@Glitchy-Sheep Just to notify, I published package to AUR.
This package should build release versions of this project.
Probably I can also add -dev-git version of package that will follow latest commit from
devbranch, but I think it's not needed for now.I suppose you are Windows user so you don't care much about it, but you may want to at least know that it exist.
@Glitchy-Sheep commented on GitHub (Aug 3, 2025):
That's actually pretty cool - thanks! :)
I noticed that the project is built for packaging. I'm not sure if it's possible, but the CI also builds the project on each release and creates a release page with a ready-to-use
.whlfile. Maybe that could simplify maintaining the AUR package, especially if dependencies change at some point.I'd love to use Linux (EndeavourOS), but I have VSTs and some specific setups on my machine that keep me from switching - for now 😄
But anyways, If you ever need any info in the future for packaging, feel free to open an issue. I'd be happy to help!
@KorespondentAda commented on GitHub (Aug 3, 2025):
I have seen this package in release, yeah, but there is an AUR specifics: if it's possible to define building from source, it's better to do so. Also used build-package routine takes care about file placement according to Arch standards and also provides
/usr/bin/boosty-downloaderconvenient launch script, so I found it easier this way.But sure, there is a way to download and package prebuilt ones, its just not preferrable because building from sources provides more options to user. Some AUR projects also provided in both forms, because it can be time-consuming to build large project than just load binaries, but there's not the case.