You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's take the example from here with postfix: #1899. postfix as an ABS package does not provide a .SRCINFO file.
I need to create it manually makepkg --printsrcinfo > .SRCINFO.
That is why, I think parsing PKGBUILD rather than .SRCINFO is easier, it could remove one step for the end user, even if it cumbersome for the yay developers and project leader.
For that reasons, the yay -Bi seems only optimized for AUR-like packages.
Then, when I do yay -Bi extra-x86_64, I get:
I added the file .SRCINFO, I could have even done other local changes but they are reversed by yay as these local changes were not committed. I don't think the git add, git commit steps should be necessary for local installs. pikaur does not have this bug.
The text was updated successfully, but these errors were encountered:
Let's take the example from here with
postfix
: #1899.postfix
as an ABS package does not provide a .SRCINFO file.I need to create it manually
makepkg --printsrcinfo > .SRCINFO
.That is why, I think parsing PKGBUILD rather than .SRCINFO is easier, it could remove one step for the end user, even if it cumbersome for the
yay
developers and project leader.For that reasons, the
yay -Bi
seems only optimized for AUR-like packages.Then, when I do
yay -Bi extra-x86_64
, I get:I added the file .SRCINFO, I could have even done other local changes but they are reversed by
yay
as these local changes were not committed. I don't think thegit add
,git commit
steps should be necessary for local installs.pikaur
does not have this bug.The text was updated successfully, but these errors were encountered: