> But if we want to get fancy, we could:
>
> 1) add a dependency on python-magic and check for text/plain
> 2) read the file line by line to see if ^pkgname= exists anywhere.
Seems like a good idea. And maybe still process as PKGBUILD when file is named
just "PKGBUILD".
On 01/25/2018 10:24 AM, Luke Shumaker wrote:
>> But it would be better to just consider every non-archive file as a
>> PKGBUILD file.
>
> +1
As I said on the bugreport:
> Personally, I wonder why we bother checking the filename at all,
> rather just assuming that the non-tar files are PKGBUILDs
On Wed, 24 Jan 2018 17:17:52 -0500,
ash...@linuxcomp.ru wrote:
>
> > How is "startswith" any less arbitrary than "endswith"? Because of some
> > habit to move PKGBUILD to PKGBUILD.suffix?
> Yes, as I already told at https://bugs.archlinux.org/task/57193:
> I keep several PKGBUILD files in one
> How is "startswith" any less arbitrary than "endswith"? Because of some
> habit to move PKGBUILD to PKGBUILD.suffix?
Yes, as I already told at https://bugs.archlinux.org/task/57193:
I keep several PKGBUILD files in one directory, and they are named like
"PKGBUILD-project1" "PKGBUILD-project2"
> Now you cannot randomly rename PKGBUILD files and use them with
> namcap. I have filed a bug here:
> https://bugs.archlinux.org/task/57193I created a patch for my
> needs:Â diff --git a/namcap.py
> b/namcap.pyindex b62a2fa..aae20c7 100755---
> a/namcap.py+++ b/namcap.py@@ -248,7 +248,7 @@
Whatever patch you were trying to post, it got lost in hoardes of div
tags.
Alad
signature.asc
Description: PGP signature
Now you cannot randomly rename PKGBUILD files and use them with namcap. I have filed a bug here: https://bugs.archlinux.org/task/57193I created a patch for my needs: diff --git a/namcap.py b/namcap.pyindex b62a2fa..aae20c7 100755--- a/namcap.py+++ b/namcap.py@@ -248,7 +248,7 @@ for package in
