Bug#707851: Debian Menu Systems : Implementation of the TC decision
On Thu, 2015-09-17 at 15:25:54 +0200, Didier 'OdyX' Raboud wrote: > > - Packages can, to be compatible with Debian additions to some window > - managers that do not support the FreeDesktop standard, also provide a > + Applications that are not registered in the desktop menu can > optionally provide a > Debian menu file, following the Debian menu policy, > which can be found in the menu-policy files in the > debian-policy package. It is also available from the Debian > web mirrors at id="http://www.debian.org/doc/packaging-manuals/menu-policy/;>. > > + > + > + Applications that are registred in the desktop menu shall not also > + provide a Debian menu file for the same application. > + > Wow, this is such terrible policy… So we have supporters of the XDG format, and supporters of the menu format. Some of those would and have accepted files of their non-preferred format in their packages, some have outright refused them. But now they have to choose between one of them, because they can no longer ship both. So we might end up with packages by menu supporters removing .desktop files, and packages from XDG supporters removing .menu files. And users of either format caught inbetween. Also is the TC going to implement the changes in the "menu programs" to support the XDG format? Because I don't see the ruling to be very motivating for the menu supporters. Regards, Guillem
Bug#792853: debian-policy: please disallow colons in upstream_version
Hi! On Mon, 2015-09-28 at 09:21:04 -0400, Sam Hartman wrote: > > "Charles" == Charles Plessywrites: > > Charles> Le Thu, Sep 24, 2015 at 03:17:30PM +0200, Jakub Wilk a > Charles> écrit : > >> * Charles Plessy , 2015-09-24, 21:53: >- > >> : ~ (full stop, plus, hyphen, colon, >+ > >> : ~ (full stop, plus, hyphen, > >> > >> Remove :, too. > > Charles> Thanks for the proofreading. > > Charles> With this correciton, are there people seconding the > Charles> proposed change ? > > > I'm totally fine with the text. > It's hard to say there's sufficient support to judge consensus with so > little discussion, but I'll second under the following rationale. > > This issue has been talked about so much, and the controversial parts > are already part of a TC decision. Hrmmm, what TC decision? Are you perhaps mixing up issues here? > If there were problems with the wording I expect someone would have > jumped up by now. > So, yeah, I think I can second. Thanks, Guillem
Bug#792853: debian-policy: please disallow colons in upstream_version
> "Guillem" == Guillem Joverwrites: Guillem> Hi! Guillem> On Mon, 2015-09-28 at 09:21:04 -0400, Sam Hartman wrote: >> > "Charles" == Charles Plessy writes: >> Charles> Le Thu, Sep 24, 2015 at 03:17:30PM +0200, Jakub Wilk a Charles> écrit : >> >> * Charles Plessy , 2015-09-24, 21:53: >- >> >> : ~ (full stop, plus, hyphen, colon, >+ >> >> : ~ (full stop, plus, hyphen, >> >> >> >> Remove :, too. >> Charles> Thanks for the proofreading. >> Charles> With this correciton, are there people seconding the Charles> proposed change ? >> >> >> I'm totally fine with the text. It's hard to say there's >> sufficient support to judge consensus with so little discussion, >> but I'll second under the following rationale. >> >> This issue has been talked about so much, and the controversial >> parts are already part of a TC decision. Guillem> Hrmmm, what TC decision? Are you perhaps mixing up issues Guillem> here? I sure am. However, I've also read the upstream colons discussion and can second that with no problems what so ever:-) (I will not second the other issue unless someone calls for seconds.) pgpkVJ9ytJ_6J.pgp Description: PGP signature
Bug#792853: debian-policy: please disallow colons in upstream_version
> "Charles" == Charles Plessywrites: Charles> Le Thu, Sep 24, 2015 at 03:17:30PM +0200, Jakub Wilk a Charles> écrit : >> * Charles Plessy , 2015-09-24, 21:53: >- >> : ~ (full stop, plus, hyphen, colon, >+ >> : ~ (full stop, plus, hyphen, >> >> Remove :, too. Charles> Thanks for the proofreading. Charles> With this correciton, are there people seconding the Charles> proposed change ? I'm totally fine with the text. It's hard to say there's sufficient support to judge consensus with so little discussion, but I'll second under the following rationale. This issue has been talked about so much, and the controversial parts are already part of a TC decision. If there were problems with the wording I expect someone would have jumped up by now. So, yeah, I think I can second. pgpLSs7pP3B2S.pgp Description: PGP signature