| 1 |
zmedico 07/09/21 23:40:17 |
| 2 |
|
| 3 |
Modified: faq.xml |
| 4 |
Log: |
| 5 |
Remove the questionable USE-deps and "Why is portage slow?" sections and remove the disclaimer="draft" guide attribute. |
| 6 |
|
| 7 |
Revision Changes Path |
| 8 |
1.25 xml/htdocs/proj/en/portage/doc/faq.xml |
| 9 |
|
| 10 |
file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml?rev=1.25&view=markup |
| 11 |
plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml?rev=1.25&content-type=text/plain |
| 12 |
diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml?r1=1.24&r2=1.25 |
| 13 |
|
| 14 |
Index: faq.xml |
| 15 |
=================================================================== |
| 16 |
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml,v |
| 17 |
retrieving revision 1.24 |
| 18 |
retrieving revision 1.25 |
| 19 |
diff -u -r1.24 -r1.25 |
| 20 |
--- faq.xml 6 Apr 2006 00:28:15 -0000 1.24 |
| 21 |
+++ faq.xml 21 Sep 2007 23:40:16 -0000 1.25 |
| 22 |
@@ -1,8 +1,8 @@ |
| 23 |
<?xml version="1.0" encoding="UTF-8"?> |
| 24 |
<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> |
| 25 |
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml,v 1.24 2006/04/06 00:28:15 chriswhite Exp $ --> |
| 26 |
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/proj/en/portage/doc/faq.xml,v 1.25 2007/09/21 23:40:16 zmedico Exp $ --> |
| 27 |
|
| 28 |
-<guide link="/proj/en/portage/doc/faq.xml" lang="en" disclaimer="draft"> |
| 29 |
+<guide link="/proj/en/portage/doc/faq.xml" lang="en"> |
| 30 |
<title>Portage Frequently Asked Questions (FAQ)</title> |
| 31 |
|
| 32 |
<author title="Author"> |
| 33 |
@@ -25,42 +25,6 @@ |
| 34 |
<chapter> |
| 35 |
<title>Frequently Asked Questions</title> |
| 36 |
<section> |
| 37 |
-<title>Why don't we have USE-based DEPEND atoms yet?</title> |
| 38 |
-<body> |
| 39 |
- |
| 40 |
-<p> |
| 41 |
-USE-based DEPEND atoms, ie DEPEND=”app-foo/bar[baz]” where baz is in IUSE of app-foo/bar are tricky to implement properly. Imagine a package with DEPEND=”app-foo/bar[baz] app-foo/coolpkg” Then in app-foo/coolpkg... DEPEND=”app-foo/bar[-baz]”. Here we have a depgraph with -baz and baz, how do we satisfy the depgraph? Also when automagically flipping flags on ( for instance, an app deps on app-foo/bar[baz] so we set USE=”baz” ) causes other fun depgraph issues and cycles. All of these must be accounted for in the code. Not to mention the depgraph code must process dependencies in a sane timeframe. |
| 42 |
-</p> |
| 43 |
- |
| 44 |
-</body> |
| 45 |
-</section> |
| 46 |
-<section> |
| 47 |
-<title>Why is portage so slow? / Why don't you rewrite portage in $RANDOM_LANGUAGE</title> |
| 48 |
-<body> |
| 49 |
- |
| 50 |
-<p> |
| 51 |
-Portage's speed (or lack thereof) has very little to do with Python the |
| 52 |
-language. The 2.0 codebase is old and was not well designed. The |
| 53 |
-developers have been talking of a redesigned codebase that attempts to |
| 54 |
-achieve many goals; being faster is one of them. For a current example |
| 55 |
-try in a shell: |
| 56 |
-</p> |
| 57 |
- |
| 58 |
-<pre caption="Pre Portage Timing"> |
| 59 |
-$ <i>time python -c 'import portage'</i> |
| 60 |
-</pre> |
| 61 |
- |
| 62 |
-<p> |
| 63 |
-On many systems this can take up to and above 10 seconds, because portage needs |
| 64 |
-to scan the tree for virtual providers and initialize all it’s configuration data. |
| 65 |
-This is just one place where older coding habits and conventions render the 2.0 |
| 66 |
-codebase difficult to work with. Zac Medico has patched the 2.1 series in a late |
| 67 |
-revision to implement lazy loading of virtuals that should speed up import times. |
| 68 |
-</p> |
| 69 |
- |
| 70 |
-</body> |
| 71 |
-</section> |
| 72 |
-<section> |
| 73 |
<title>Can I mount the portage tree ( /usr/portage ) via NFS?</title> |
| 74 |
<body> |
| 75 |
|
| 76 |
|
| 77 |
|
| 78 |
|
| 79 |
-- |
| 80 |
gentoo-commits@g.o mailing list |
Archives