Linux Factory Packages

Registered by Scott James Remnant (Canonical) on 2008-11-18

Discuss Scott's idea to have a linux-factory package containing compiled-but-not-linked .o files for the kernel image; on installing, the link is performed, building in drivers according to a configuration file

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

Related branches

Sprints

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/updates/proposed/security.

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

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.