Linux Factory Packages
Discuss Scott's idea to have a linux-factory package containing compiled-
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Whiteboard
I'm not sure if this is even feasible. Would require the source as well, since the .o files for modules are compiled with different defines than if they are built-in. You can't just change how it's linked.
Doing this would also create a rather large package, on the order of 80-100Megs. Archive admins are sure to complain about having 3-4 of these things available, especially across stable/
In addition, I'm not sure the benefit would even warrant it. With the assumption that we are already going to be changing a good portion of common modules to built-in, there's only a very small niche of users that would want this, and even then, they are likely going to compile their own kernel, rather than use this (as the overhead is relatively the same for them).
Just my two cents...BenC
