From a9a33765e779bf000d2cf5355cf5650b3d27ecd3 Mon Sep 17 00:00:00 2001 From: Markus Meier Date: Fri, 4 Jun 2010 23:08:07 +0200 Subject: move autopackage to src_prepare --- .../functions/src_prepare/autopackage/text.xml | 42 ++++++++++++++++++++++ 1 file changed, 42 insertions(+) create mode 100644 ebuild-writing/functions/src_prepare/autopackage/text.xml (limited to 'ebuild-writing/functions/src_prepare/autopackage/text.xml') 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 @@ + + + +Autopackage + + +

+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. +

+ +

+Autopackage packages are totally unsuitable for Gentoo systems for a +large number of reasons: +

+ +
    +
  • + To even unpack the package, you must run arbitrary code supplied by an untrusted source. +
    • +
  • They install directly to the live filesystem.
    • +
  • Their intrinsic dependency resolver is broken.
    • +
  • They do not support the filesystem layout used by Gentoo.
    • +
  • They do not support configuration protection.
    • +
  • They can clobber arbitrary files on uninstall.
    • +
  • The linking mechanism used is insufficiently flexible.
    • +
  • + The entire format is completely unportable and highly tied to x86 + Linux systems. +
    • +
+ +

+Upstream are aware of these issues and have no desire to fix them +indeed, they pass off some of their most broken behaviour as +'features'. +

+ + + -- cgit v1.2.3-65-gdbad