On Sep 22, 2007, at 8:46 AM, David Golden wrote:
On 9/21/07, Michael G Schwern <[EMAIL PROTECTED]> wrote:
Michael G Schwern wrote:
Hmm. I just noticed that I set 'no_index' for the src directory
which
contains the SVN:: modules which brings up the interesting
question of which
takes precedence, no_index or provides?
Since provides is explicit, I'd say it should override the more
general no_index.
My understanding is that these serve two different purposes.
"provides" indicates what modules are included in the tarball so that
tools don't have to unpack the tarball to understand the contents.
The meaning of "provides" is very specific: if a distribution
provides Foo::Bar and you want Foo::Bar, you can install that
distribution.
My understanding is that "no_index" is only useful when "provides"
isn't there and an indexer has to guess what you provide. When
"provides" is there, it should be exhaustive. Note that the spec
says "indexers will usually trust the C<provides> field if it's
present." That's just a recommendation from me to the owners of the
indexers, but I think it's one they follow.
So in Schwern's case, "provides" should indeed win, and furthermore
you should be able to just remove "no_index" altogether.
-Ken