Re: Is menu orphaned? (Was: Debian Menu transition status)
On Mon, 3 Dec 2007, Bill Allombert wrote:
Indeed another conclusion you just drawn was that I never actually
received your email. I am not subscribed to debian-devel, and I
did not post to that list. Instead I posted to debian-devel-announce.
My email ended in debian-devel for reasons I did not anticipate.
I will resend it to debian-devel-announce.
Well, my understanding of debian-devel-announce is that it is
for important announcements and debian-devel is for discussing
thise announcements. That's why I suggested that somebody should
read possible replies to his announcements (even if I admit that
a CC in this special case would have been reasonable).
Generally, if you want to reach me, please email me directly.
Lesson learned. ;-)
On the other hand, I am currently lacking a menu developer with a good
understanding of C++, which delays the resolution of some bugs, but if
you just want to help me with menu QA, you are welcome too.
I had a look into menu code but realised that my poor C++ knowledge
is probably not enough.
The menu format that is currently used by nearly every package
was obsolated by the menu-2 format two years ago because the
information about was so perfectly hidden that nobody really
noticed.
menu-1 format is not obsoleted.
Well, I admit I'm failing to find the quote - I probably imagined
to have read it was obsoleted.
There must be a first time for everything. But try
Yes, this is right.
grep "menu-2" /etc/menu-methods/*
My problem is that after 8 years the first menu file that is
actually using it broke a script in cdd-common and I have no
idea how to fix this because there is no description of this
format.
I don't see how it is relevant to debian-policy or dh-make.
You don't want to tell me that #447389 and #447390 make no
sense.
I have no feeling about using menu-2 for menu file, but I recommend
it for menu-methods.
But why?
Thanks for explaining to this list all the trouble I had to
get through before discovering menu-2.
??
I don't understand this statement?
So how could you expect developers to adopt a new format if there
is no information about it?
By posting to debian-devel-announce.
After 8 years and without drawing the consequences to file the
apropriate bug reports especially #447391? This sounds not very
convincing.
Apparently one is not allowed to post a followup to a previous
debian-devel-announce post, even if it is two month old. I did
not anticipated that.
Well, my first posting had a delay of eleven days and both are
listed at
http://lists.debian.org/debian-devel/2007/10/threads.html
in the very same thread. (BTW, I'm keen on the explanation why
your original posting does not show up in debian-devel-announce
archive but in debian-devel exclusively.)
Assuming your menu-1 file has a single entry, this is sufficient.
(Else you obviously need one ';' for each entry).
Well, to come to a productive suggestion: If menu-2 just adds
some syntax sugar that makes no real advantage - could we just
drop this new and unknown format? Would this have any bad
consequences (except of rewriting some menu methods)?
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: