Re: [arch-projects] [namcap] [PATCH 0/4] Add a rule against common filenames in source() without overridden name

2019-05-26 Thread James Harvey via arch-projects
On Sun, May 26, 2019 at 10:45 PM Eli Schwartz via arch-projects wrote: > All your patches show up as attachments, which makes it difficult to > review, and they don't show up in patchwork. > > Generally speaking, the most reliable way to send a patch is by using > `git send-email`. Sorry about

Re: [arch-projects] [namcap] [PATCH 0/4] Add a rule against common filenames in source() without overridden name

2019-05-26 Thread Eli Schwartz via arch-projects
On 5/26/19 10:35 PM, James Harvey via arch-projects wrote: > There's no good way for namcap to ensure source() filenames are unique > across all packages, required for users with SRCDEST. But, I think by > far the most common offending filename would be LICENSE, as > non-standard ones are

[arch-projects] [namcap] [PATCH 0/4] Add a rule against common filenames in source() without overridden name

2019-05-26 Thread James Harvey via arch-projects
There's no good way for namcap to ensure source() filenames are unique across all packages, required for users with SRCDEST. But, I think by far the most common offending filename would be LICENSE, as non-standard ones are required to be included, but sometimes there's no upstream tarball or