On Mon, Jul 09, 2012 at 08:03:21PM +0200, Matteo Bernardini wrote: > > 2. For manually compiled and installed programs, the user needs to > > call the menu generation tool, which is very bad. > > I agree, also it would probably need to run it as root to do it system-wide.
Being root or non-root is hardly relevant in this case. When a user makes a program available to others, this can be accomplished either in "pull" or "push" way. "pull" means that those interested in the program do something actively (e.g. modify their PATH or their menu) before they can use the program; "push" means that the user has modification privileges to some part of the concerned users' environment, like write access to a directory in their PATH. "superuser" is just one fashion (and most often a too heavy one) of many possible ways to influence other users' program setup without asking them for cooperation. You face the privilege administration problem anyway, either you use menus or not. Cheers Rune ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Lxde-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lxde-list
