On 13/07/14 21:01, Karanbir Singh wrote:
On 07/13/2014 01:24 AM, Trevor Hemsley wrote:
On 28/06/14 11:44, Anssi Johansson wrote:
Please note that some install options will automatically pull in some extra packages. For example, installing on an encrypted filesystem will pull in some packages, and installing on software RAID will pull in some another set of packages. Here's a list of packages that I think are one way or another affected by this (and their dependencies):
chrony cryptsetup cryptsetup-libs device-mapper-event device-mapper-event-libs device-mapper-persistent-data dosfstools efibootmgr grub2 grub2-efi grubby libreport-filesystem lvm2 lvm2-libs mdadm mokutil shim shim-unsigned
I would suggest making sure these packages get included, otherwise some functionality of the installer may break.
anaconda also mentions realmd. I suppose it would get installed if anaconda needs to access an Active Directory server during installation. That package depends on PackageKit-glib, libarchive, oddjob, oddjob-mkhomedir and psmisc. I don't have an AD server here at home, but I suppose it'd work like http://fedoraproject.org/wiki/QA:Testcase_realmd_join_kickstart
I did a minimal install under VBox this evening then ran yum install for the 18 packages listed above. 8 of those were already installed so this added 10 to the mix. I didn't include the ones listed as Active Directory. I then ran this in the Packages dir of the DVD1 with just the rpm names in my txt file:
$ for f in $(cat /tmp/rpmnames.txt); do ls -la $f-[0-9]*; done > /tmp/rpmnls.txt $ awk '{ n += $5 } END { print n }' /tmp/rpmnls.txt 210154444
I've now attached that list to my mail in the format discussed on IRC. If I'm right about 210MB then I don't think space on a CD will be too much of a problem but let's wait and see what it turns out like once it's built ;-)
We pushed and did some initial testing around a minimal build last night on irc. the builds were pushed to http://buildlogs.centos.org/centos/7/isos/x86_64
It does not have the anaconda changes we typically do with the minimal install, but otherwise it should be a complete build at 565MB in size.
please test it, its essential that we get as wide a testing base and options / variations as possible.
Well, it crashes for me .. I'll compare the packages list you have used, as it seems less than the normal @core minimal set, which was supposed to be the target (well, in fact *more* packages than just @core, as some deps are needed when using luks/mdadm/btrfs/mdadm, and so on ...) I'll come back with a list and also reading the whole thread about packages people were mentioning