[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[p2-dev] A typical use-case
- From: Thomas Hallgren <thomas@xxxxxxx>
- Date: Sun, 26 Feb 2012 14:22:05 +0100
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.1) Gecko/20120209 Thunderbird/10.0.1
1. I'm downloading and installing Eclipse Classic 3.7.2.
2. I'm installing something from Indigo.
At step 2, I'm forced to wait while all children of the Indigo release are downloaded. Why? I'm only interested in SR2.
The previous releases will just a) take a long time to download, and 2) consume a lot of memory when perused.
I know there are cases where someone would like to revert to a previous install etc. and that all previous releases
therefore must be available, but what I can't understand is why this must control the default behavior for the 99% of
the users that never needs that. Why not let releases/indigo appoint the last release and have something like
releases/indigo-with-legacy appoint the composite?