| 1 |
Ian Stakenvicius wrote: |
| 2 |
|
| 3 |
>> "Such data is locally generated ... The application must be able |
| 4 |
>> to regenerate or restore the data." |
| 5 |
> |
| 6 |
> emerge --sync <-- regenerates/restores the portage tree |
| 7 |
|
| 8 |
Perhaps my English is too poor, but IMHO |
| 9 |
download != regenerate/restore. |
| 10 |
|
| 11 |
Indeed, the FHS also emphasizes only the *time* which it costs |
| 12 |
to regenerate the data in /var/cache and that it can be deleted |
| 13 |
without data loss (e.g. if your filesystem runs full). |
| 14 |
|
| 15 |
However, if you would do this e.g. on a laptop because you |
| 16 |
blindly trusted FHS you may have a lot of problems: Not only |
| 17 |
can it be quite expensive to "regenerate" the data |
| 18 |
(e.g. if you have to pay a lot for the bandwidth where you |
| 19 |
currently are), it might even be impossible if you have no |
| 20 |
internet connection at all or e.g. if you realize only after |
| 21 |
the deletion that you would have to (re)emerge some package to |
| 22 |
make the internet connection work (e.g. because you did not |
| 23 |
revdep-rebuild before). |
| 24 |
|
| 25 |
(And, yes, if you deal with distdir carefully, there are several |
| 26 |
occassions when you might want to (re)emerge a package even if |
| 27 |
you have no or only very limited internet connection; not only for |
| 28 |
revdep-rebuild but also e.g. if you need to change certain USE-Flags.) |
| 29 |
|
| 30 |
Of course, an experienced user knows and can care about this all, |
| 31 |
but an experienced user will choose the location anyway as he needs: |
| 32 |
We are speaking about the default which should mainly help also the |
| 33 |
less experienced user. |
| 34 |
|
| 35 |
> download-restricted data whose sole location is in a cache dir is a |
| 36 |
> decision made by the user. |
| 37 |
|
| 38 |
If you make /var/cache/... the default, this suggests the wrong |
| 39 |
decision to the user. At least, it should be documented then in |
| 40 |
a prominent place that the default path where the data is |
| 41 |
required is probably not the appropriate path to keep it |
| 42 |
(which IMHO is a bit strange). |
| 43 |
|
| 44 |
> [...] PORTAGE_RO_DISTDIR [...] Maybe it would be pertinent to |
| 45 |
> suggest and/or include a default path for this? |
| 46 |
|
| 47 |
This would be a good idea anyway, also because of theoretically |
| 48 |
possible name collisions in distdir. |
| 49 |
|
| 50 |
Martin |
Archives