You are not logged in.
long time AUR "leecher". But want to send some patches up.
Should I create my repo on arch's gitlab and then send a patch to the maintainer?
If starting a new package, is it OK to host on arch's gitlab from the beginning?
If not, open gitlab/hub/berg is OK?
Those practical considerations are not covered on the sticky here or at the wiki. I don't want to believe everyone maintains those packages alone with local repos and communicating via ...I don't know how since most AUR users email are hidden (good, but). Is that what the "package actions > submit request > merge request type" is for?
Last edited by gcb (2024-05-22 18:31:30)
Offline
I think you mix two things here.
Archlinux Packages are hosted on Gitlab now, but AUR is seperate from that, so I don't really now what you mean and what you want to do.
Regarding regular packages you can probably file a bugreport first.
Regarding AUR you can leave a comment.
But I am sure a mod will also answer your question.
Offline
but AUR is separate from that, so I don't really now what you mean and what you want to do.
I mean, create a repo under my user for the AUR repo that will have the PKGBUILD file. Thinking in terms of a healthy ecosystem, it is more likely that someone sending patches to AUR will have an arch gitlab account than some random code host service.
Regarding AUR you can leave a comment.
Forgot about comments when I wrote it went that route.
Thanks
Last edited by gcb (2024-05-22 19:34:23)
Offline
As there is no integration between AUR and Arch's gitlab instance there is no current difference between sending a patch from Arch's gitlab and any other code host; they all have to be provided as a link to some text file or reference a commit ID in a different git.
Offline
thanks loqs. I'm aware of no integration, was more asking about usage rules for gitlab instance. is it OK for AUR code? or reserved for already approved packages?
Offline