On Mon, 12 Aug 2019 21:33:52 +0300 Paul Finkelshteyn <pavel.finkelshtein@gmail.com> wrote:
On Mon, 12 Aug 2019 14:23:51 -0400 Eli Schwartz via aur-general <aur-general@archlinux.org> wrote:
On 8/12/19 2:12 PM, Paul Finkelshteyn wrote:
On Mon, 12 Aug 2019 14:03:55 -0400 Eli Schwartz via aur-general <aur-general@archlinux.org> wrote:
Hi folks,
As kodi-devel-bin take almost forever to build I've created github https://github.com/asm0dey/arch-kodi-devel-builder/ with pre-built packages.
Now I want to create AUR packages which will be able to install these binary packages.
No.
Basically it's why I'm writing here
And thank you for asking first! :)
As you can see I have some knowledge on how to maintain packages: https://aur.archlinux.org/packages/?SeB=m&K=asm0dey but in this concrete situation I have no any idea on how to create packages. Of course I can't just use these packages in source field because they have their own dependencies. Also I think I can't just install them inside build or package phase…
So question is: is there any recommended way to do what I want?
If you replace the word "recommended" with the word "allowed", then the answer is "you are allowed to advertise your repository on https://wiki.archlinux.org/index.php/Unofficial_user_repositories and on the package details for the AUR package".
In fact, you're actually encouraged to do so. That's why we have the wiki listing in the first place. :)
But truth is I don't have repository (cause repository should have some predefined layout and so on). And I'm not sure if it's possible to create something repository-like on github. And I currently I have no idea on where should I have to host repository for it to be more or less reliable.
I think you can probably use github pages for this. Github already allows release assets, and there are definitely people putting release assets in github pages, so I don't think this is against the terms of service, and github pages lets you provide a simple html index and file structure however you like.
Just make sure to rebuild and force overwrite the gh-pages branch rather than appending new commits, to make sure the size doesn't get too big due to bloaty binary blobs in git history.
Sounds awful cause it will bloat repo size to insane sizes (built packages are tens of MB) and it's devel version so it may obtain updates several times a week…
OK it looks like there is no sane way to do what I want so maybe I should just leave it as repo-for-myself.
Paul
Oh I see, you're telling about rewriting commits. It may make sense, but will take wome time to implement. Should think about it, thanks Paul