Date: Wed, 15 Jan 2014 11:17:10 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Rusmir Dusko <nemysis@FreeBSD.org> Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r338572 - head/games/palomino Message-ID: <20140115111710.GA50575@FreeBSD.org> In-Reply-To: <20140113104200.GA80610@nemysis4now> References: <20140113104200.GA80610@nemysis4now>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Jan 13, 2014 at 11:42:00AM +0100, Rusmir Dusko wrote:
> In my earlier email correspondence with makcs regarding DESKTOP_ENTRIES,
> he stated some interesting arguments, as to why would one, do so.
>
> This is from his last email:
>
> > I suppose you simply removed 'false', so that DESKTOP_ENTRIES had only 5
> > elements. If you need empty field, you shall use double quotes (""), e.g:
> >
> > DESKTOP_ENTRIES= "Name" "" "Icon" "Exec" "Categories" ""
> >
> > This desktop entry will use ports ${COMMENT} for second field, and empty
> > StartupNotify field.
I've played a bit with DESKTOP_ENTRIES, it seems that ${COMMENT} is indeed
gets added by default, so "" is okay. As for StartupNotify, it also looks
like that forcing it to 'false' might be in fact wrong. Per specification:
"If true, it is KNOWN that the application will send a "remove" message
when started with the DESKTOP_STARTUP_ID environment variable set. If
false, it is KNOWN that the application does not work with startup
notification at all (does not shown any window, breaks even when using
StartupWMClass, etc.). If absent, a reasonable handling is up to
implementations (assuming false, using StartupWMClass, etc.)"
That said, emptying ${COMMENT} and 'false' values looks correct. Thanks
for the insight.
./danfe
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140115111710.GA50575>