Re: [aur-general] Updating AUR versions server side

> > [...] I believe the .SRCINFO file was added so that the AUR could discover > > a PKGBUILD's version without needing to evaluate arbitrary scripts. > > As far as I know the AUR did not, at any point, evaluate arbitrary > scripts to retrieve metadata. It did parse (or attempt to...) the >

Re: [aur-general] Updating AUR versions server side

> > What if regular, non development, AUR packages were tested server side > > for new versions? > > Won't that make more sense than the maintainer having to run pkgver() > > manually from time to time? > > We shall not evaluate user-uploaded shellscripts on the AUR server. Most > AUR helpers

Re: [aur-general] TU membership application

> > Well, I think it should be the other way around, you first mentor someone > > and look with them into their packages and then decided about sponsorship. > > That's your opinion, and here's mine: I don't think that's important. If a > candidate looks promising and there is an intention to both

Re: [aur-general] Deletion of discord-updater{,-canary}?

> The pkgver() function is ran after the sources are downloaded. So > doing source=('$pkgname-$pkgver::url') will not work. Thanks though. Pooh. Gotcha.

Re: [aur-general] Deletion of discord-updater{,-canary}?

> Adding a pkgver() to Discord in a clean way is proving to be quite annoying. > Adding this to the source=() > 'https://discordapp.com/api/download/canary?platform=linux=tar.gz' > causes makepkg to download a file named 'canary?platform=linux=tar.gz' > even though the download output from curl

Re: [aur-general] TU Application: Andrew Crerar

> ttf-google-fonts-git: > - `install -dm755 ...; install -Dm644 ...;` is kind of like sprinkling > your code with `sleep 1` (I think) I understand what you mean, but Andrew might not. To put a finer point on it, `install -dm755` is unnecessary, because install's `-D` flag creates directories

Re: [aur-general] pisg-fixed

> > well, i beg your pardon if i made the assumption that TU and the entire > AUR structure was smart enough to understand a merge request of a > differently-owned package as an orphan request for a clearly fixed package. > > i humbly beseech myself towards your graces and fall upon my sword for >

Re: [aur-general] TU Application: Morten Linderud

> > python-vagrant: > > - test cases could be run > > - you could distribute the LICENSE.MIT file as MIT is not a common > > The testing is sorta peculiar as it requires vagrant and virtualbox(!) to run. > Haven't gotten the cases to run after installing them so I have to work a bit > more on

Re: [aur-general] TU Application: Thore Bödecker

> And on my router at home. Neat! What are you using for router hardware? I've done this as well. I used a desktop with ethernet and wifi expansion cards for several years, and then moved to a PC Engines apu2c2 . It seems like you have a good set of system