[arch-general] [arch-dev-public] Namcap release coming soon

[Dan McGee]

On Tue, Jun 8, 2010 at 10:15 AM, Guillaume ALAUX <guillaume at alaux.net> wrote:
> On 8 June 2010 16:58, Dan McGee <dpmcgee at gmail.com> wrote:
>
>> On Tue, Jun 8, 2010 at 9:56 AM, Dan McGee <dpmcgee at gmail.com> wrote:
>> > Forwarding to the public list is your best option; going to one
>> > developer is a good way for your email to get lost.
>> >
>> > ---------- Forwarded message ----------
>> > From: Guillaume ALAUX <guillaume at alaux.net>
>> > Date: Tue, Jun 8, 2010 at 9:54 AM
>> > Subject: Re: [arch-dev-public] Namcap release coming soon
>> > To: dpmcgee at gmail.com
>> >
>> >
>> > Hi Dan,
>> > Didn't really how to answer your mail as I don't have write access to
>> > the list so I'm just answering directly to you:
>> >> If anyone [...] knows of very small issues that need fixing ...
>> > When namcap'ing a package including scripts that use '#!/bin/sh'
>> > instead of '#!/bin/bash', output is something like the following:
>> > pkgname E: Dependency detected and not included (sh) from files
>> ['script.sh']
>> > (I know the AL standard page on the wiki says we should use bash
>> > rather than sh but these are scripts included in the original
>> > tarball.)
>> > As we don't have any sh package that error sounds strange to me (I
>> > have this "issue" on one of my packages in AUR)
>> > Should we change these scripts so that they use bash instead of sh or
>> > should we change namcap in order for it not to yield such error?
>>
>> Namcap needs to be fixed to recognize provides. The bash package
>> currently provides sh, so there should be no error here.
>>
>> -Dan
>>
>
> Well even though bash provides sh (as a link), namcap says "Dependency
> detected and not included (sh) from files"
>
> See the comments on one of my AUR package:
> http://aur.archlinux.org/packages.php?ID=37110

Yes, I understand this. We don't care at all about links or anything
in the filesystem; we are simply looking for an 'sh' package that
doesn't exist. Until namcap can do reverse provides matching (e.g.
look for a package that provides 'sh'), then this won't work. Of
course, you can always just make your package depend on 'sh'.

The depends module is extensive and has a lot to it, so this is not
going to be a quick/easy change.

-Dan