Arch Linux User Repository

Before running makepkg add Mike Fährmann's key

gpg --recv-keys 5680CA389D365A88

@m040601 For a package to be included in the official repos, it is entirely up to an official package maintainer to be interested in it.

Just a question out of curiosity.

This PKGBUILD has been on the AUR for 7 years. Well cared for and maintained. It has a lot of votes also.

In my opinion should be an official Arch package.

Is there a reason why no official package maintainer has picked it up yet ? Lack of interest ?

Could it be because the tool powerfully scrapes a lot of websites and there is some "gray area" with licenses/terms of use ???

Funny because yt-dlp does the same for videos and is an official Arch package.

Thanks for the prompt positive response !! Realy nice.

don't write whole essays about such simple things 

Your're 100 % right. I actually hesitated. The thing is I've been asking the same thing to other PKGBUILD maintainers. And have gotten responses, specially from younger ones, like ... Why ? You can read "in the browser" ? You can do "git log" ... etc

@m040601 I've added configuration.rst,formatting.md,gallery-dl-example.conf to /usr/share/doc/gallery-dl. That should be enough for most cases.

As for the license not being included, that is not needed for "common licenses", see https://wiki.archlinux.org/title/PKGBUILD#license. But as a side effect of using python-build, it gets included anyway in /usr/lib/python3.13/site-packages/gallery_dl-1.29.5.dist-info/licenses/LICENSE

Also please don't write whole essays about such simple things next time, it only makes it much harder to get to what the point is.

Detailed explanation of my previous comment.

pacman -Ql gallery-dl

gallery-dl /usr/bin/gallery-dl
.....
gallery-dl /usr/lib/python3.13/site-packages/gallery_dl/
.....
loooooooootz of stuf
.....
gallery-dl /usr/share/bash-completion/completions/gallery-dl
gallery-dl /usr/share/fish/vendor_completions.d/gallery-dl.fish
gallery-dl /usr/share/zsh/site-functions/_gallery-dl
.....
gallery-dl /usr/share/man/man1/gallery-dl.1.gz
gallery-dl /usr/share/man/man5/gallery-dl.conf.5.gz
.....

Good. We get the bin "gallery-dl", some very nice shell completions, and 2 man pages. That's what the "doctor" ordered.

The "doctor" in this case are all the steps using "make" and "python build/installer". They obey and do what is prescribed in the repo own "recipees". The recipees are the "Makefile" and "setup.cfg/setup.py" controlled by the developer. They are a Linux generic thing. Not an Archlinux specific thing.

build() {
    ....
    make
    python -m build .......
}

check() {
    make ....
}

package() {
    python -m installer ...
}

The Archlinux specific thing is this PKGBUILD. We control it here and choose what to do. Add more salt, put less sugar etc. Not the gallery-dl developer. We can choose to install any extra file XYZ.txt in folder FOOBAR, even if the gallery-dl didnt say choose to do that. It is our computer.

Let's have a look at what is available in the repo at any time,

source = git+https://github.com/mikf/gallery-dl.git#tag=v123.FOO.BAR.?signed

git clone https://github.com/mikf/gallery-dl.git

......
          docs                                                                 10
......
          CHANGELOG.md                                                      323 K
......
          LICENSE                                                          17.7 K
......
          README.rst                                                       13.2 K
......

1. README

That README.rst has some examples and details not on the man page. In an ideal world the man page would have everything you need. No extra "tips" or "secrets" in some other place. But that's not the case.

1. LICENSE

Strangely we dont get any "/usr/share/licenses/gallery-dl/LICENSE ???

1. CHANGELOG

I find that file EXTREMELY usefull to keep up with such a fast changing tool like this one. Otherwise I miss important stuff and cool new things.

Lets have a look at that "docs" folder

_layouts
configuration.rst                                                 182 K
formatting.md                                                    13.3 K
gallery-dl-example.conf                                          14.4 K
gallery-dl.conf                                                  24.3 K
index.md                                                          305 B
links.js                                                         1.08 K
oauth-redirect.html                                               244 B
options.md                                                         10 K
supportedsites.md                                                42.5 K

So it contains files for generating the online website (ex _layouts, links.js, index.md). These are not important for us.

But. Again, it also contains some interesting files

1. "gallery-dl.conf"

a complete example with options set to their default values,

1. "gallery-dl-example.conf"

a configuration file example with more involved settings and options,

1. "configuration.rst"

lists all available configuration options and their descriptions.

Again, these extensive and detailed informations is not on the man pages.

It could be, but it isnt yet. Thats the job for the developer.

In the meantime we could have them on our Archlinux computer in "/usr/share/doc/gallery-dl". It will certainly not "blow up" the storage space with a meager KBytes of plain text files.

Thanks for the work maintaining the PKGBUILD for this extremelly usefull tool.

The tool itself has a man page and even online documentation. But. There are still some example files and detailed information not present on those man pages. And I would also like to have them offline on my computer, not beeing forced to go online to read them.

A list of all available configuration options and their descriptions
can be found at https://gdl-org.github.io/docs/configuration.html

I personally hate this. Being forced to open a web browser just to learn to use a cli tool. When i could have that tiny size plain text or markdown file (or html) stored locally on my computer.

TLDR:

Please add some extra step on the PKGBUILD to make sure they land on the Archlinux computer. Something simple like "install -Dm644 xyz ... foo ... bar"

/usr/share/doc/gallery-dl/README.rst
/usr/share/doc/gallery-dl/CHANGELOG
/usr/share/doc/gallery-dl/gallery-dl.conf 
/usr/share/doc/gallery-dl/gallery-dl-example.conf"
/usr/share/doc/gallery-dl/configuration.rst
...
/usr/share/doc/gallery-dl/LICENSE

@katt OK. Your prerogative. I maintain it doesn't make much sense here.

It does for projects that don't actually make releases and only create the tags or projects outside github for example.

@vcalv Because I prefer it and one makedep which you probably already have anyway doesn't matter. Also makepkg supports checksums since a long time now . I will not include this "fix".

Also several packages in the official repos do the same, there is nothing wrong doing it this way.

Why is this downloading the source code via git?

It should use something like https://github.com/mikf/gallery-dl/releases/download/v1.29.4/gallery_dl-1.29.4.tar.gz

One less dependency and also allows for checksum verification.

It should be trivial to fix.

This pkgrel should be bumped to 2 to force a rebuild against python 3.13.