Tiziano Müller wrote:
Doug Goldstein wrote:
Tiziano Müller wrote:
Donnie Berkholz wrote:
Hi all,
Here is the summary from Thursday's council meeting. The complete log
will show up at http://www.gentoo.org/proj/en/council/ shortly.
wrt GLEP 56:
i) I don't see a specification when use.local.desc is finally going to be
dropped
ii) Why not switch to XML for use.desc as well? (just to be consequent)
We could then use XInclude in a package's metadata.xml to include a
global use.desc.xml in <use>...</use>
(The requirements could then be changed to: the USE flags description has
to be written in the packages metadata.xml)
Incremental steps are better then one huge sweeping change. It'll allow
us to evaluate the needs and goals of the project as we move forward.
I agree.
The big concern with dropping use.desc is that multiple USE flags that
do the same thing will start to pop up across the whole tree because
developers won't know that a USE flag already exists for feature X.
I'd not drop use.desc, I'd substitute it with an XML-based file using a
similar (or the same) syntax as metadata.xml.
But instead of having the package manager (or other tools operating with USE
flags/USE flag descriptions) to lookup in either a package's metadata.xml
_or_ a global use.desc.xml, I'd use XInclude in metadata.xml (which then
includes the global use.desc.xml) such that the package manager (or other
tools) just have to consider a package's metadata.xml.
This approach would make it possible to have more than one use.desc.xml.
For example for kde or gnome related global USE-flags: kde.use.desc.xml or
gnome.use.desc.xml.
If you write the code....
That's the biggest issue with features and ideas people propose. No one
is willing to sit down and write the code necessary. Look at how many
GLEPs set unimplemented because of lack of code.
This also involves increasing the XML support in every package manager,
which is not going to be a small undertaking.
--
gentoo-dev@lists.gentoo.org mailing list