|
Lines 297-302
so that you can tidy up, file a bug.
Link Here
|
| 297 |
</body> |
297 |
</body> |
| 298 |
</section> |
298 |
</section> |
| 299 |
|
299 |
|
|
|
300 |
<section> |
| 301 |
<title>VCS Ebuilds</title> |
| 302 |
<body> |
| 303 |
|
| 304 |
<p> |
| 305 |
VCS Ebuilds should always be masked or without keywords. This applies to |
| 306 |
"live" ebuilds (-9999*) or ebuilds that use a "VCS tag" or such to provide |
| 307 |
some pseudo version-like number but still uses VCS to fetch. |
| 308 |
</p> |
| 309 |
|
| 310 |
<p> |
| 311 |
Keeping a VCS ebuild visible (non-masked) is bad for a couple of reasons, |
| 312 |
here are a few that have been expressed by users: |
| 313 |
</p> |
| 314 |
|
| 315 |
<ul> |
| 316 |
<li> |
| 317 |
Cannot "emerge -f" while online then emerge while offline. Pulling from |
| 318 |
VCS breaks this. |
| 319 |
</li> |
| 320 |
<li> |
| 321 |
Some machines are behind firewalls that are restrictive. Users should |
| 322 |
expect all non-masked ebuilds to be fetched on common mirroring ports, |
| 323 |
eg port 80 from distfiles.gentoo.org |
| 324 |
</li> |
| 325 |
</ul> |
| 326 |
|
| 327 |
</body> |
| 328 |
</section> |
| 329 |
|
| 300 |
</body> |
330 |
</body> |
| 301 |
</chapter> |
331 |
</chapter> |
| 302 |
</guide> |
332 |
</guide> |
| 303 |
- |
|
|
