On Sun, Jan 11, 2004 at 01:15:09AM +0100, Jan Schulz wrote: > Hallo! > > * Karl Trygve Kalleberg <[EMAIL PROTECTED]> wrote: > > We have a similar (currently unsolved problem) with Eclipse; it updates > > itself from the net, bypassing portage entirely. > > I have a patch for that. Available from the debian patches and in the > eclipse BTS (search for 'Plugin dir in $HOME'). Mail me, if you want > it. Content:
(Got the patch from eclipse bug #36101). > * set up the main site (/usr/share/eclipse) as 'read only' > * adds a new option to include new sites at runtime (-addsite <path>) > > Drawbacks: updatemanager (in 2.1) becomes mostly useless with this, as > it doesn't recognise sites, which are setup via 'links' files (see > below). > > You also can setup plugin location by using this syntax: > /usr/share/eclipse/links/something.links > |path=r /usr/local/share/ > (note the 'r ', will expect 'eclipse/features and eclipse/plugins in > there) I guess your solution to this is a close to perfect as we can get. Regular users should not be allowed to install system-wide available packages in /usr (depending on site policy they may do so in /usr/local). Thus we should aim for allowing users to install plugins for themselves (probably somewhere in their home directory), or in a directory shared by a particular group of users. Also, I suppose we may want to add a minor UI patch to notify users that 'Gentoo-supported' plugins are installable using Portage (or apt-get, for Debian). Kind regards, Karl T -- [EMAIL PROTECTED] mailing list
