From: Thomas L. <ta...@ec...> - 2005-10-27 20:37:18
|
On Thu, Oct 27, 2005 at 04:21:27PM -0400, Keith Warno wrote: > I liked it much better when 0install was an option. Nowadays it has > become a requirement for certain functionality. Sigh. It's only a requirement for things that weren't possible before anyway. You haven't lost any functionality. Also, it should be possible to integrate support with RPM, so that installing something with RPM will add it as a feed for 0launch. For example, 'rpm -i rox-filer.rpm' could create a file called /etc/xdg/0install.net/injector/user_overrides/...ROX-Filer.xml pointing to the feed in /usr/share/rox. Then, if a program tried to run ROX-Filer using: $ 0launch http://rox.sourceforge.net/2005/interfaces/ROX-Filer it could use the version installed by the RPM. OTOH, this seems a bit complicated. Why not just use a custom version of 0launch that only trusts keys in /etc/0install/sysadmin_trusted_keys, instead of letting users specify their own lists? That will stop (non-expert) users from installing software from dodgy sites. You could get it to display a box "This software is not approved. Please contact sys...@ex... if you need to use it.". > Anyway, the point is the ROX-Filer/AppRun tries to grab the ROX > mime-info via 0install. If it can't get it via 0install, it doesn't > bother to get it, or say anything about not being able to get it. So, > if I'm not mistaken, if ROX-Filer is not installed system-wide via the > likes of the install script or something that does the > update-mime-database, the user will have issues like Ken's. Already fixed in CVS. -- Dr Thomas Leonard http://rox.sourceforge.net GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1 |