[Feature Request] Work with custom `PKGBUILD`s

[stevenxxiu]

Have you checked the readme and man page for this feature? Yes.

Have you checked previous issues for this feature? Yes.

Besides the packages that I installed in AUR, I also have some custom Git packages that aren't in the AUR. (The reason they aren't, is because they're packages with some custom patches of mine, so I don't think they're applicable to everyone.)

I used to have a Python script that just checks if these packages are out-of-date, and updates them if they are. But I think it's much more convenient to use Paru for this instead.

I symlinked my custom packages into ~/.cache/paru/clone/, and updated ~/.cache/paru/devel.json. I discovered today that Paru doesn't appear to check updates for these packages despite there being an update in the package's Git repo.

Debugging this, it appears that Paru did indeed see an update and put it in the updates variable in devel.rs's possible_devel_updates(). However it seems that the function filter_devel_updates() in devel.rs removes any non-AUR package.

Can there be a way to allow Paru to include custom PKGBUILDs, and upgrade those packages too?

I quite love Paru, thanks for making it!

[Morganamilo]

Paru can only check updates from the aur. Supporting external sutff is out of scope and won't be implemented unless maybe it can be done in a clean way that integrates well.

[stevenxxiu]

Here I'm just interested with Git packages. So I just need to pretend the package is in the AUR.

Correct me if I'm wrong, but I think this will be fine if filter_devel_updates() doesn't trim any package if it's not in the AUR. I think then the modification to Paru is really quite small.

Would that be alright?

[Morganamilo]

For starters paru relies on the aur metadata to get info about a package.

-U can deal with pkgbuilds but it's special cased. I would like to make that more general at some point. That would have to be done first.

[Morganamilo]

So this is a milestone for v2, which is still a while off. But as of now this is basically fully functional in paru-git

Add:

[REPONAME]
Git = https://github.com/user/pkgbuilds/

To your paru.conf and there you have it

You will need to run paru -Sya so sync these repos.

You can then install packages with paru -S foo or paru -S REPONAME/foo.

There's a few extra options to configure this.

• Depth configures how deeply to recurse to find pkgbuilds, the default is 3.
• SkipReview can be specified in the repo to skip the review process for just that repo`.
• GenerateSrcinfo force generates srcinfo files, this is for is a repo has outdated srcinfo files.
• Path can be specified instead of Git to point to a local file path.

There's no documentation on this as of yet as it's very much beta, but feel free to test it out.

[Seqularise]

What about build order? Personally for me repo specific option with list of packages would be cool enough, i could finally ditch my script to build most of kde

[Morganamilo]

Repo is top priority, then custom repos, then aur

[Seqularise]

I mean inside this custom repo, if i have in this repo pacman-git and paru-git i want to build pacman first

[Morganamilo]

Well it builds packages based on what targets you give, not the whole thing at once. But paru shouldn't build something without solving deps anyway.

[mio-19]

So this is a milestone for v2, which is still a while off. But as of now this is basically fully functional in paru-git

Add:

[REPONAME]
Git = https://github.com/user/pkgbuilds/

To your paru.conf and there you have it

You will need to run paru -Sya so sync these repos.

You can then install packages with paru -S foo or paru -S REPONAME/foo.

There's a few extra options to configure this.

• Depth configures how deeply to recurse to find pkgbuilds, the default is 3.
• SkipReview can be specified in the repo to skip the review process for just that repo`.
• GenerateSrcinfo force generates srcinfo files, this is for is a repo has outdated srcinfo files.
• Path can be specified instead of Git to point to a local file path.

There's no documentation on this as of yet as it's very much beta, but feel free to test it out.

I am getting error: unknown section error. It the syntax changed?

[Morganamilo]

Are you running paru-git?

[stevenxxiu]

When updating to a new Paru commit https://github.com/Morganamilo/paru/commit/d97bb0a7c346660d9166f1fd4583d8530677a14f recently, my custom repo is no longer recognized.

My /etc/paru.conf looks like:

...

#
# Custom Repo
#
[steven]
Depth = 1
SkipReview
Path = /home/steven/os/linux/dev/packages/

Update:

My bad, setting Depth = 2 fixes things.