Bill Anderson wrote:
Given the comments on DHCP client, here is the new list I propose:
So...making the leap of faith assumption that this list of packages to "fix" the current minimal install option is a best effort attempt.
Some basic questions follow...how much smaller is this really making the minimal harddrive footprint? And is anyone willing to build up a prototype comps.xml file associated this initial "correction" list, that doesn't break the other currently available install types?
-jef
On Thu, 2003-08-21 at 19:39, Jef Spaleta wrote:
Bill Anderson wrote:
Given the comments on DHCP client, here is the new list I propose:
So...making the leap of faith assumption that this list of packages to "fix" the current minimal install option is a best effort attempt.
Some basic questions follow...how much smaller is this really making the minimal harddrive footprint?
I Don't know, I'm about minimizing the software, not necessarily the space used.
And is anyone willing to build up a prototype comps.xml file associated this initial "correction" list, that doesn't break the other currently available install types?
I am working on modifying the comps.xml file, indeed already have a couple of patches, depending on the choices made.
Since these changes take place *only* in the Minimal group, they will *only* affect that group, no other group requires Minimal that I have seen yet [quick double-check] yes, this group is not required by any other group. OS changes to *this* group affect *only* this group.
Minimal install is not a Type of install, it is a group you select. I see Types as "Server", "Workstation", etc..
Right now, I am working ona python script that explores a given group and determines a package list for the entire group. With this, my goal is (initially) to be able to have it take the Mandatory, and later Default, options in the group, list them, and then follow it's group requirements and do the same up the tree (all the way to Core).
However, I am also working on my wife's OOo install right now, so it will be later tonight.
On Thursday 21 August 2003 18:48, Bill Anderson uttered:
I am working on modifying the comps.xml file, indeed already have a couple of patches, depending on the choices made.
Since these changes take place *only* in the Minimal group, they will *only* affect that group, no other group requires Minimal that I have seen yet [quick double-check] yes, this group is not required by any other group. OS changes to *this* group affect *only* this group.
Minimal install is not a Type of install, it is a group you select. I see Types as "Server", "Workstation", etc..
While it is a group, it's not a defined group in the comps.xml file I was looking at. Is it defined in the beta? Shamefully I"ve been looking at teh RHL9 comps.xml since that was what was handy.
Some of our changes will effect the Base and Core groups, possibly the Dialup group as well. I feel these changes are necessary, but will effect all other groups, since all other groups will require the Core and Base group. Maybe I'm off base here, but I'll await your comps.xml changes.
On Thu, 2003-08-21 at 23:08, Jesse Keating wrote:
On Thursday 21 August 2003 18:48, Bill Anderson uttered:
I am working on modifying the comps.xml file, indeed already have a couple of patches, depending on the choices made.
Since these changes take place *only* in the Minimal group, they will *only* affect that group, no other group requires Minimal that I have seen yet [quick double-check] yes, this group is not required by any other group. OS changes to *this* group affect *only* this group.
Minimal install is not a Type of install, it is a group you select. I see Types as "Server", "Workstation", etc..
While it is a group, it's not a defined group in the comps.xml file I was looking at. Is it defined in the beta? Shamefully I"ve been looking at teh RHL9 comps.xml since that was what was handy.
Sorry, yes I've been going on the beta. In the beta, it is a group defined in the comps.xml file.
Some of our changes will effect the Base and Core groups, possibly the Dialup group as well. I feel these changes are necessary, but will effect all other groups, since all other groups will require the Core and Base group. Maybe I'm off base here, but I'll await your comps.xml changes.
Actually, I don't expect much changes in other groups, though rerunning the build tools will be needed to verify. I've got a script that can track package/group requirements based solely on the comps.xml file.
My wife, however, is cracking the ol' whip and I need to get some sleep in. I'll have the changed comps.xml file tomorrow. And hopefully, a (cgi) script that lets you click through groups, etc..
Cheers, Bill
-
Bill Anderson -
Jef Spaleta -
Jesse Keating