PKGBUILD reviewing process

[ljmf00]

There are a few questions I want to come up with in terms of the PKGBUILD reviewing process:

• This will be the default behavior, although it will appear on every PKGBUILD or only the explicitly specified packages? Dependencies are shown by default or prompt?

I also propose the usage of ranger as an optional dependency for pretty reviewing and fallback to less
if ranger is not present.

ranger view example:

less view example:

[FFY00]

We open it in $EDITOR, also allowing it to be modified.

[ljmf00]

We open it in $EDITOR, also allowing it to be modified.

Sure, but isn't preferred to analyze every file contained in the PKGBUILD context, like the local sources?

[FFY00]

Sure, but we should still force the user to actually see the PKGBUILD by default. I think we should open the PKGBUILD in $EDITOR and then have a prompt asking if the user whishes to review the rest of the files. This would default to no, and when selected would run xdg-open /path/to/review/stuff.

[ljmf00]

Sure, but we should still force the user to actually see the PKGBUILD by default. I think we should open the PKGBUILD in $EDITOR and then have a prompt asking if the user whishes to review the rest of the files. This would default to no, and when selected would run xdg-open /path/to/review/stuff.

👌