Re: about commit debian-edu r40399
- To: José L. Redrejo Rodríguez <email@example.com>
- Cc: Custom Debian Distributions <firstname.lastname@example.org>
- Subject: Re: about commit debian-edu r40399
- From: Andreas Tille <email@example.com>
- Date: Thu, 28 Feb 2008 11:35:41 +0100 (CET)
- Message-id: <alpine.DEB.1.00.0802281129290.3199@wr-linux02>
- In-reply-to: <1204193249.9493.9.camel@aula1-pro>
- References: <1203598980.18675.40.camel@aula1-pro> <alpine.DEB.1.00.0802280907040.3199@wr-linux02> <1204193249.9493.9.camel@aula1-pro>
On Thu, 28 Feb 2008, José L. Redrejo Rodríguez wrote:
I do fully agree with you. I don't feel confortable with that hack nor
with the way I've included the icons for the menu branches. I've opted
for the 'known to work correctly today' solution, but more ellegant and
robust solutions should be found.
I can perfectly cope with a "works for the moment" solution. I just
wanted to trigger a discussion in which direction to move development.
Anyway, your doubts link with the message I sent last week to the
debian-custom mailing list. Obviously this is something to be done on
cdd. My doubts are that maybe the option of choosing between a
recommendation or a dependency should be implemented. For this case, it
should be recommends, but maybe we should leave open both options for
I agree that we might need both Depends and Recommends (perhaps even
suggests), but in this specific case I wonder what harm will be done
if we Depends from the menu stuff. I would regard it important enough
to Depend from it. Do you see any strong reason to be able to remove
the menu package?
On the other hand, as this email goes also to debian-custom, maybe we
could also work on taking this freedesktop menu changes to cdd, together
with the debian menu changes you've already done. Actually, I don't know
if freedesktop menus changes make sense in other cdd's, but if they do,
looking for common points would save work for we all.
It _definitely_ makes a strong reason and I would have implemented
it long before if I would have had enough knowledge about this before.
I also putted debian-custom in CC in my first mail because I think it
should be discussed here. I even stopped CCing debian-edu which I
only included because the problem occured in the debian-edu source