aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorMarkus Meier <maekke@gentoo.org>2010-06-04 23:08:07 +0200
committerMarkos Chandras <hwoarang@gentoo.org>2010-08-24 12:46:19 +0300
commita9a33765e779bf000d2cf5355cf5650b3d27ecd3 (patch)
tree31b965ae47022ed061ca01eeba560fca78aa4aef /ebuild-writing/functions/src_prepare/autopackage/text.xml
parentdelete (diff)
downloaddevmanual-a9a33765e779bf000d2cf5355cf5650b3d27ecd3.tar.gz
devmanual-a9a33765e779bf000d2cf5355cf5650b3d27ecd3.tar.bz2
devmanual-a9a33765e779bf000d2cf5355cf5650b3d27ecd3.zip
move autopackage to src_prepare
Diffstat (limited to 'ebuild-writing/functions/src_prepare/autopackage/text.xml')
-rw-r--r--ebuild-writing/functions/src_prepare/autopackage/text.xml42
1 files changed, 42 insertions, 0 deletions
diff --git a/ebuild-writing/functions/src_prepare/autopackage/text.xml b/ebuild-writing/functions/src_prepare/autopackage/text.xml
new file mode 100644
index 0000000..dfde1c5
--- /dev/null
+++ b/ebuild-writing/functions/src_prepare/autopackage/text.xml
@@ -0,0 +1,42 @@
+<?xml version="1.0"?>
+<guide self="ebuild-writing/functions/src_unpack/autopackage/">
+<chapter>
+<title>Autopackage</title>
+
+<body>
+<p>
+If a package is only supplied in autopackage format, you must not add
+it to the tree. If a package is supplied in autopackage format and
+some other sane standard format (for example a source tarball), use
+the other format only.
+</p>
+
+<p>
+Autopackage packages are totally unsuitable for Gentoo systems for a
+large number of reasons:
+</p>
+
+<ul>
+ <li>
+ To even unpack the package, you must run arbitrary code supplied by an untrusted source.
+ </li>
+ <li>They install directly to the live filesystem.</li>
+ <li>Their intrinsic dependency resolver is broken.</li>
+ <li>They do not support the filesystem layout used by Gentoo.</li>
+ <li>They do not support configuration protection.</li>
+ <li>They can clobber arbitrary files on uninstall.</li>
+ <li>The linking mechanism used is insufficiently flexible.</li>
+ <li>
+ The entire format is completely unportable and highly tied to x86
+ Linux systems.
+ </li>
+</ul>
+
+<p>
+Upstream are aware of these issues and have no desire to fix them <d/>
+indeed, they pass off some of their most broken behaviour as
+'features'.
+</p>
+</body>
+</chapter>
+</guide>