diff options
| author |   Tavis Ormandy <taviso@gentoo.org> | 2003-07-02 23:27:55 +0000 |
|---|---|---|
| committer | Tavis Ormandy <taviso@gentoo.org> | 2003-07-02 23:27:55 +0000 |
| commit | b6db9daf3eedb02273ce4ec335b2bccf354f82e6 (patch) | |
| tree | 5d2c66c70fc77599d4d61a766484b1315c66da23 /sys-apps | |
| parent | added metadata.xml (diff) | |
| download | historical-b6db9daf3eedb02273ce4ec335b2bccf354f82e6.tar.gz historical-b6db9daf3eedb02273ce4ec335b2bccf354f82e6.tar.bz2 historical-b6db9daf3eedb02273ce4ec335b2bccf354f82e6.zip | |
metadata
Diffstat (limited to 'sys-apps')
| -rw-r--r-- | sys-apps/milo/Manifest | 3 | ||||
| -rw-r--r-- | sys-apps/milo/metadata.xml | 12 |
2 files changed, 14 insertions, 1 deletions
diff --git a/sys-apps/milo/Manifest b/sys-apps/milo/Manifest index 66c7a4f843b2..4c898e24651c 100644 --- a/sys-apps/milo/Manifest +++ b/sys-apps/milo/Manifest @@ -1,5 +1,6 @@ -MD5 ae83855cebf2c7772bcb102ce298ea77 milo-2.4.18.ebuild 8113 +MD5 a8c2f9dc2988688b2990dccdd2f3cbc0 milo-2.4.18.ebuild 8113 MD5 51d36e2f8c42a6385f9c8e041e698cea ChangeLog 849 +MD5 382a839b2dd3b36aee659eba1be42e2d metadata.xml 752 MD5 987873fb766bc62dcb7336015388e4e3 files/mkserial_no.c 1264 MD5 d3af0c52f49dbc1430e1ed77878273c5 files/milo-2.2-18-gcc3-gentoo.diff 5624 MD5 f6830f117d7528a50b53e85150040d73 files/linux-2.2.25-gcc3-milo.diff 3542 diff --git a/sys-apps/milo/metadata.xml b/sys-apps/milo/metadata.xml new file mode 100644 index 000000000000..1f77966e45f9 --- /dev/null +++ b/sys-apps/milo/metadata.xml @@ -0,0 +1,12 @@ +<?xml version="1.0" encoding="UTF-8"?> +<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> +<pkgmetadata> +<herd>no-herd</herd> +<maintainer> + <email>taviso@gentoo.org</email> + <name>Tavis Ormandy</name> +</maintainer> +<longdescription> +On Intel based PC systems, the BIOS firmware sets up the system and then loads the image to be run from the boot block of a DOS file system. This is more or less what MILO does on an Alpha based system, however there are several interesting differences between BIOS firmware and MILO, not least of which is that MILO includes and uses standard Linux device drivers unmodified. MILO is firmware, unlike LILO, which relies on the BIOS firmware to get itself loaded. +</longdescription> +</pkgmetadata> |