| 1 |
I've been running my latest install with features=test, makes it |
| 2 |
simple to test packages requiring stablizization and all that... at |
| 3 |
least partially.. |
| 4 |
|
| 5 |
However, I've seen a few packages that fetch stuff during the test |
| 6 |
phase from the internet, which seems like a _really_ bad idea to me. |
| 7 |
For 1, what if I -f while dialed up and then disconnect, and for two, |
| 8 |
what happens if the site it's connecting to is down? These can both |
| 9 |
effect the outcome of my emerge. |
| 10 |
|
| 11 |
So far, I've seen one of each |
| 12 |
libxml2 fetches a DTD, it fetched fine, but if I had not had |
| 13 |
internet... it probably would have died, a simple possible fix to this |
| 14 |
is to add the dtd to SRC_URI, but this an extra thing to handle for |
| 15 |
people without FEATURES="test", and without feature-specific deps |
| 16 |
(farily useless overall), there would have to be a USE="test" to take |
| 17 |
advantage of this. |
| 18 |
|
| 19 |
The other is net-misc/neon, this one has a down upstream server, and |
| 20 |
the build died because of this |
| 21 |
|
| 22 |
Only way I can think of to fix this is to disable the test. |
| 23 |
|
| 24 |
|
| 25 |
Test policy seems fairly vague in general, maybe this is a good time |
| 26 |
to clarify//enforce it? |
| 27 |
|
| 28 |
Opinions? Comments? Flames? |
| 29 |
|
| 30 |
Thats what the mailing list is for! |
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives