| 1 |
On Tue, 09 Mar 2004 12:36:17 -0800 |
| 2 |
Jason Rhinelander <jason@××××××××××××××××.com> wrote: |
| 3 |
|
| 4 |
> How is that broken behaviour? If a non-cvs ebuild can't download its |
| 5 |
> sources, it fatals as well. |
| 6 |
> |
| 7 |
|
| 8 |
The difference is that with usual ebuilds, you can "emerge -f" from your |
| 9 |
laptop when it's connected for instance at your work, or download |
| 10 |
source archives from a friend's computer and use a removable device, |
| 11 |
etc. There are a lot of such workaround that make _possible_ to use |
| 12 |
ebuilds for people who don't have internet at home, but none of the |
| 13 |
usual and simple ones apply to cvs ebuilds because they fetch at |
| 14 |
src_unpack time. Not really a broken behavior tho, but may be annoying |
| 15 |
for some people. Also, the fact that you have to cvs update when you do |
| 16 |
a revdep-rebuild despite you've not deleted anything from your distfiles |
| 17 |
is a unexpected behavior. Maybe the eclass could take a CVS_NO_UPDATE |
| 18 |
environnement variable into account that would force the ebuild to use |
| 19 |
the repository in its current state instead of updating? That would |
| 20 |
easily solve the above issues. |
| 21 |
|
| 22 |
-- |
| 23 |
TGL. |
| 24 |
|
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives