Re: [gentoo-dev] about non-ebuild files in the tree (and verification thereof)

[Fabian Groffen]

On 28-02-2018 22:08:54 +0000, Robin H. Johnson wrote:
> On Wed, Feb 28, 2018 at 04:10:52PM +0100, Fabian Groffen wrote:
> > Hi,
> >
> > I'm working on a verification implementation of
> > https://www.gentoo.org/glep/glep-0074.html and ran into the following
> > scenario that I don't know if it's right or wrong:
> ...
> > Does anybody know or have a pointer to what the policies on files in our
> > ebuild dirs actually is?
> PMS, 4.3 Package directories:
> A package directory may contain other files or directories, whose
> purpose is not covered by this specification.

Ah, forwards compatibility.

> GLEP74 itself makes no determination of files being permitted in a given
> directory.
>
> > Now in a rsync checkout of the Prefix tree, where my own implementation
> > also runs the fat manifest creation, this entry is not present, because
> > I always believed only metadata.xml, ChangeLog* and *.ebuild files were
> > allowed.
> I'd say your separate implementation is wrong in this case, but that
> file also should not permit at this time.

I might change it not to bother about what should be in/out, but just
assume it's right as-is.  For now it is a nice headsup about something
being unexpected.

> > Now I'm confused as to whether this is the case or not, I can't find a
> > GLEP or anything, but repoman also is as happy as it can be on this odd
> > file (I thought it used to complain about stray/unadded files).
> I personally think repoman should complain about it because it's weird.

I'm sure this particular file was a mistake, that went unnoticed for a
very long time.  I do feel this should one way or the other not be
allowed.

Thanks for your insights,
Fabian

-- 
Fabian Groffen
Gentoo on a different level