*subsequent* SW install won't add new entries to "Applications" menu
glgxg at sbcglobal.net
Sun Sep 11 17:20:05 UTC 2011
On 09/11/2011 09:49 AM, Robert P. J. Day wrote:
> On Sun, 11 Sep 2011, NoOp wrote:
>> On 09/11/2011 09:21 AM, Robert P. J. Day wrote:
>> > On Sun, 11 Sep 2011, Liam Proven wrote:
>> >> Have you tried doing some detective work and discovering how it's
>> >> actually installed, so that you can go looking for config files and
>> >> so on elsewhere?
>> > this is proprietary software whose entire install appears to do
>> > little more than dump everything into a single directory, so i don't
>> > see what i did as being that drastic.
>> > in fact, what i did appears to work just fine in terms of just
>> > deleting the entire install directory and re-installing. the *only*
>> > issue is that, the first time i installed, i got those Applications
>> > menu entries; since then, i haven't, so i'm just curious as to how a
>> > *normal* ubuntu install would check whether those entries need to be
>> > added.
>> > i'm in the midst of some detective work doing just what you suggest,
>> > but i'm asking what appears to be a general question -- if a ubuntu
>> > package wants to add an entry to the Apps menu, where would it
>> > normally check to see if that's already been done? other than that
>> > hiccup, everything else seems to be behaving just fine.
>> Most likely a leftover entry in:
> yup, that looks like the offending directory, which has remnants of
> numerous earlier versions of the same software as well. i'm assuming
> that, as long as none of the entries in that dir actually show up in
> my Apps menu, i'm safe to simply manually delete them, yes?
Yes. But generally I rename them first (just in case). Example:
OOo-Dev.desktop to x-OOo-Dev.desktop-x
I use that naming convention because then it's easy for me to go back
later and just delete the 'x-<file>-x' files.
More information about the ubuntu-users