Difference between revisions of "Talk:Dependency and versioning"
From Organic Design wiki
(archive old notes) |
m (Caretaker: headings) |
||
| Line 2: | Line 2: | ||
Having produced the basis of a bootable operating system with a working Perl interpreter, a shell and a file system in RAM, the next major problem to solve is dependency and versioning. | Having produced the basis of a bootable operating system with a working Perl interpreter, a shell and a file system in RAM, the next major problem to solve is dependency and versioning. | ||
| − | + | = Problems = | |
At a low level we must consider these factors: | At a low level we must consider these factors: | ||
* The version of the linux kernel we are using (currently a custon 2.4 kernel) | * The version of the linux kernel we are using (currently a custon 2.4 kernel) | ||
| Line 13: | Line 13: | ||
* How to do all this without making the OS too big | * How to do all this without making the OS too big | ||
| − | + | = Possible solutions = | |
* Use of an existing repository such as debian to ensure all the binaries play happily with each other. | * Use of an existing repository such as debian to ensure all the binaries play happily with each other. | ||
* Use a combination of apt and dpkg to filter out documentation and other unnecessary files | * Use a combination of apt and dpkg to filter out documentation and other unnecessary files | ||
| Line 19: | Line 19: | ||
* Compile everything from scratch ourselves (any volunteers?) | * Compile everything from scratch ourselves (any volunteers?) | ||
| − | + | = Thoughts = | |
The binary part of the perl modules would have to be compiled againast the same libc with the same gcc as the other binaries. Perhaps we can use a ppm repository like activestate to obtain pre-compiled binaries. | The binary part of the perl modules would have to be compiled againast the same libc with the same gcc as the other binaries. Perhaps we can use a ppm repository like activestate to obtain pre-compiled binaries. | ||
Latest revision as of 22:45, 12 November 2006
Archive
Having produced the basis of a bootable operating system with a working Perl interpreter, a shell and a file system in RAM, the next major problem to solve is dependency and versioning.
Problems
At a low level we must consider these factors:
- The version of the linux kernel we are using (currently a custon 2.4 kernel)
- The version on libc we are using
- The version of libc (and gcc) our binaries are compiled against
At the application level we must consider:
- How to solve dependancy problems to that all the required libraries are available
- How to do this for Perl so perl modules can be retrieved and used in the same way
- How to do all this without making the OS too big
Possible solutions
- Use of an existing repository such as debian to ensure all the binaries play happily with each other.
- Use a combination of apt and dpkg to filter out documentation and other unnecessary files
- Perhaps build a minimal repository for our use based on one of the bigger distros
- Compile everything from scratch ourselves (any volunteers?)
Thoughts
The binary part of the perl modules would have to be compiled againast the same libc with the same gcc as the other binaries. Perhaps we can use a ppm repository like activestate to obtain pre-compiled binaries.
