On 17 May 2012 20:32, Dave Abrahams <
dave@...> wrote:
>
> on Thu May 17 2012, Thomas Leonard <talex5-AT-gmail.com> wrote:
>
>> On 26 April 2012 06:54, Dave Abrahams <
dave@...> wrote:
>>>
>>> As an experiment, I thought maybe I'd try throwing out my
>>> ~/.cache/0install.net and doing an autocompile. Here's what happened:
>> [...]
>>> Is ~/.config/0install.net/0compile/builds some kind of a cache?
>>
>> It contains the generated feeds, one per version, which point to
>> implementations under ~/.cache.
>>
>> Which isn't very sensible. Probably we should put builds under
>> ~/.local somewhere and have 0install add them as feeds automatically,
>> without needing them to be registered explicitly. Then you could
>> remove one just by deleting its directory. Currently, you have to
>> unregister the feed, remove the feed from ~/.config, and remove the
>> implementation from the cache if you want to get rid of everything
>> cleanly.
>
> Yeah, I've had a lot of trouble getting back to a clean state if, e.g. I
> have fixed a tool I used to do a build and need to repeat it.
I've created an experimental branch ("site-packages") of 0install
which automatically adds to an interface (URI) all feeds from:
XDG_DATA_DIRS/0install.net/site-packages/URI/VERSION/0install/feed.xml
There is a corresponding "site-packages" branch in 0compile which
copies builds to there instead of the cache.
This means:
- wiping the cache doesn't destroy local builds
- deleting the VERSION directory completely removes a build; no need
to unregister the feed as well
Note that I also changed the name of the generated feed files.
0compile used to create 0install/NAME.xml (e.g.
0install/ROX-Filer.xml). That was confusing to new users (looking for
something to add for "Add Local Feed") and made it hard for tools to
find the feed automatically. Now it creates "0install/feed.xml"
always.
There are a number of issues still to think about:
- "0compile register" should also use this, not just "autocompile".
- 0compile shouldn't do this unless the system 0install is new enough
to use it; need to think about a backwards compatible way to do the
migration.
- if you registered a 0install/NAME.xml as a feed, you need to
unregister it and add 0install/feed.xml instead. We might want to
automate that.
- we could possibly use this to replace the native_packages thing:
/usr/share/0install.net/native_feeds/INTERFACE
becomes
/usr/share/0install.net/site-packages/INTERFACE/native_feed/0install/feed.xml
--
Dr Thomas Leonard
http://0install.net/GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1
GPG: DA98 25AE CAD0 8975 7CDA BD8E 0713 3F96 CA74 D8BA
------------------------------------------------------------------------------
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/_______________________________________________
Zero-install-devel mailing list
Zero-install-devel@...
https://lists.sourceforge.net/lists/listinfo/zero-install-devel