Bug 364047

Summary:	equery meta reports missing metadata.xml if an overlay is missing but main tree has
Product:	Portage Development	Reporter:	Serkan Kaba (RETIRED) <serkan>
Component:	Third-Party Tools	Assignee:	Portage Tools Team <tools-portage>
Status:	CONFIRMED ---
Severity:	normal	CC:	dan
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Serkan Kaba (RETIRED) gentoo-dev

2011-04-18 15:55:48 UTC

Pating conversation in #gentoo-dev

<Serkan> equery meta reports missing metadata.xml if I have an overlay with missing metadata.xml should having one in main tree suffice?
<Serkan> should/shouldnt?
<fuzzyray> Serkan: There can be two opinions there.  One is that since it is an overlay, the metadata.xml from the tree may not be correct and thus not used. Second, it's the same package so use it.
<fuzzyray> We could probably do a middle ground, where we fall back to the main tree and use it, but indcate that it is from the tree and not the overlay
<jmbsvicetto> Serkan: all overlays I work with have a metadata.xml even if it's the same as the one in the tree (kde, desktop-effects, mysql)
<Serkan> jmbsvicetto: it's a local overlay where I do my development, anyway just wanted to report the issue
<jmbsvicetto> Serkan: I also have metadata.xml for my personal overlay
<fuzzyray> Serkan: Would you be willing to file a bug?
<Serkan> fuzzyray: yeah actually I would ask that
<fuzzyray> It's working as designed, but I can see changing it
<dberkholz> i guess i'd treat it the same as ebuilds