summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris PeBenito <pebenito@gentoo.org>2003-10-25 21:40:11 +0000
committerChris PeBenito <pebenito@gentoo.org>2003-10-25 21:40:11 +0000
commit2502106561d14ecaf1f8f0e6d4465212720d9b28 (patch)
tree453788430844370510eacd99c95a2ea591c3294c /sys-apps/mkinitrd
parentFix stupid typo in the gcc-3.2 check so that pentium4 flags still wouldn't be... (diff)
downloadgentoo-2-2502106561d14ecaf1f8f0e6d4465212720d9b28.tar.gz
gentoo-2-2502106561d14ecaf1f8f0e6d4465212720d9b28.tar.bz2
gentoo-2-2502106561d14ecaf1f8f0e6d4465212720d9b28.zip
update metadata
Diffstat (limited to 'sys-apps/mkinitrd')
-rw-r--r--sys-apps/mkinitrd/Manifest6
-rw-r--r--sys-apps/mkinitrd/metadata.xml8
2 files changed, 10 insertions, 4 deletions
diff --git a/sys-apps/mkinitrd/Manifest b/sys-apps/mkinitrd/Manifest
index fed66ffcf092..c2070e7cccd0 100644
--- a/sys-apps/mkinitrd/Manifest
+++ b/sys-apps/mkinitrd/Manifest
@@ -1,7 +1,7 @@
+MD5 c30cd3a38b3468cf6f0144a2dd4a99fc mkinitrd-3.5.7-r1.ebuild 1067
MD5 fb3902e22a198853ff021ddac9d85e2f ChangeLog 938
-MD5 17b4958b2bb0b4700e0ab8cdb753b9f6 metadata.xml 397
+MD5 80d5be275d0b73e0d36e0ebd4239abf5 metadata.xml 600
MD5 166f29ba80d7acdafd51cbcbed61b79a mkinitrd-3.5.7.ebuild 927
-MD5 c30cd3a38b3468cf6f0144a2dd4a99fc mkinitrd-3.5.7-r1.ebuild 1067
-MD5 1a8259233cb009f44a8fe20a8aa828b5 files/digest-mkinitrd-3.5.7 66
MD5 0bc4fe62070fcfc54254d0e8c636ef32 files/mkinitrd-selinux.diff 1007
MD5 1a8259233cb009f44a8fe20a8aa828b5 files/digest-mkinitrd-3.5.7-r1 66
+MD5 1a8259233cb009f44a8fe20a8aa828b5 files/digest-mkinitrd-3.5.7 66
diff --git a/sys-apps/mkinitrd/metadata.xml b/sys-apps/mkinitrd/metadata.xml
index 1407b7d04f88..3012f8d0de45 100644
--- a/sys-apps/mkinitrd/metadata.xml
+++ b/sys-apps/mkinitrd/metadata.xml
@@ -7,5 +7,11 @@
<name>Chris PeBenito</name>
<description>Maintainer</description>
</maintainer>
-<longdescription>Mkinitrd creates initial ramdisks for use when the kernel first loads.</longdescription>
+<longdescription>
+Mkinitrd creates filesystem images for use as initial ramdisk (initrd)
+images. These ramdisk images are often used to preload the block
+device modules (SCSI, RAID or LVM) needed to access the root filesystem.
+
+Mkinitrd also does the inital policy load for SELinux users.
+</longdescription>
</pkgmetadata>