summaryrefslogtreecommitdiff
path: root/sys-boot/milo/metadata.xml
diff options
context:
space:
mode:
Diffstat (limited to 'sys-boot/milo/metadata.xml')
-rw-r--r--sys-boot/milo/metadata.xml16
1 files changed, 9 insertions, 7 deletions
diff --git a/sys-boot/milo/metadata.xml b/sys-boot/milo/metadata.xml
index a9870c74849d..987a57516414 100644
--- a/sys-boot/milo/metadata.xml
+++ b/sys-boot/milo/metadata.xml
@@ -1,11 +1,11 @@
<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<!DOCTYPE pkgmetadata SYSTEM "https://liguros.gitlab.io/dtd/metadata.dtd">
<pkgmetadata>
- <maintainer type="project">
- <email>alpha@gentoo.org</email>
- <name>Gentoo Linux Alpha Development</name>
- </maintainer>
- <longdescription lang="en">
+ <maintainer type="project">
+ <email>alpha@gentoo.org</email>
+ <name>Gentoo Linux Alpha Development</name>
+ </maintainer>
+ <longdescription lang="en">
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,
@@ -14,4 +14,6 @@
Linux device drivers unmodified. MILO is firmware, unlike LILO, which
relies on the BIOS firmware to get itself loaded.
</longdescription>
-</pkgmetadata>
+
+ <origin>gentoo-staging</origin>
+</pkgmetadata> \ No newline at end of file