[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Feedback about the cdd-dev package and more...

|--==> Andreas Tille writes:

  AT> On Fri, 3 Dec 2004, Free Ekanayaka wrote:
  >>Task: mytask1
  >>Description: bla bla
  >>Depends: pkg1 (relevance=10, menu=Some/Custom/Path), pkg2 (relevance=6, menu=Some/Other/Path)
  AT> If you ask me this is a strange way to specify the menu path.  I found out that
  AT> substituting the maintainers menu path by <task>/remaining path is mostly fine.
  AT> If it is not, just provide an override.  This leaves a minimum of work for the
  AT> CDD maintainer (who can start without any work and just fix something which does
  AT> not fix the expectations).

  >>So  when  you want to add  a  package you have to  add  it both to the
  >>pseudo-control file (in  the Depends: stanza of some  task) and in the
  >>menu tag file,

  AT> No. The task file is enough.

I guess,  it's  enough only if   you want  to replace   just the first
component of the menu path:


but what if  I want completely  custom  menu entries? Actually I  need

  >>and if another information   comes out in future  in a
  >>third file an so on.. Isn't that clean. Am I missing something?
  AT> In case of another information you are perhaps right.



Reply to: