From: Andrew F. <an...@bl...> - 2004-05-21 09:57:11
|
On 2004-05-20, Thomas Leonard <ta...@ec...> wrote: > [snip] > > You're right that self-compiling from zero install doesn't work > automatically at the moment for ROX-Filer. You have to drag the filer to > your home directory, click on it, and then use 0divert to redirect to your > new copy. Is there a need for someone to write a nice GUI for 0divert? (Having never used it myself), or even Filer integration somehow? > For relocation, app dirs have only ever allowed you to move directories > that you own. Otherwise, you have to copy. Having Edit in Zero Install is > no different from having Edit in /usr/local/apps in this regard: as a > user, you can't modify either of them, but you can make a copy in your > home directory and modify that. Yes, of course. >> > (answer: use the configured one, or a default if none is configured) >> >> Any thoughts on how this configuration could work? Debian uses its >> /etc/alternatives, but `update-alternatives' isn't very user friendly >> IME. > > See http://www.freedesktop.org/Standards/config-spec Interesting. > If you want to run a modified version of a library, just click on it and > it can make itself the default. Until then, it shouldn't be assumed that > the user wants it (even if it is 'safe'; it might be the wrong version). How? Whether or not the Filer does this automatically or provides a way for AppDirs to register themselves as "seen" (or it happens automatically upon running, either way...) it still doesn't bypass the problem that unless the app does something evil like persistently make itself default by some form of symlink in a fixed location (eg. ~/lib) there's no way for an app using that library to know that there's a new default it should use. > Otherwise, we'll get in to the RISC OS problem of applications fighting > over who handles what. True. But there are some hard issues to solve here, I don't think (in the long term) they can be solved by saying "the user has to configure whatever they want". Admittedly, distributions should be configuring defaults, which may point into ZeroInstall, however if AppDirs are a suitable replacement for RPMs, debs etc. then we can't rely on `apt-get install some-rox-app' modifying the appropriate files for shared mime info. Also, having code in each app to provide the user the option of sticking some symlinks in CHOICESPATH/MIME-Types/ seems like a redundant duplication of code. > Well, you're talking about new systems. For backwards compatibility, of > course we support other systems. But Zero Install is designed to fix > exactly the problems you're describing, so why not use it? True. Perhaps I'm not thinking fourth dimensionally^W^WZeroInstall enough. > The easy solution to your problem is to get whatever brings the network up > and down (which must run as root) to modify wgetrc (or some more general > location) at the same time. It really should do this anyway, or other > programs (wwwoffled, etc) will stop working too. You could also make a > wrapper script for wget that tests the network state. True. I think I might have to start writing a ROX network configuration tool as there doesn't seem a way of configuring in any of the existing ones "when this network comes up, if the IP address matches "9.*" then set the system proxy to xxx, run this script, make the toast, etc." > Changing an environment variable to reflect the new network situation is a > hack, and will cause other problems, including: you have to logout when > changing the settings, other users don't get the updates, daemon processes > stop working, etc. However since wget and other tools such as lwp-request (in fact LWP::*.pm) don't support the (seemingly) hypothetical fd.o config spec (yet), but do support the (standard) http_proxy variable it is currently the best way. The rest of the problems aren't a concern (in my usage) for my laptop. It gets shut down between home and work, I'm the only user etc. > Again, this is probably something you want to store in a general > configuration system. Agreed. But then everything'll need wrappering, or porting, to use it. Not that that's a bad thing, just that it needs doing :) Cheers, Andrew -- Andrew Flegg -- mailto:an...@bl... | http://www.bleb.org/ |