Changes between Version 8 and Version 9 of Obsolete/MovedToTree/PackageManagement/OldIdeas
- Timestamp:
- Aug 5, 2009, 7:47:13 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Obsolete/MovedToTree/PackageManagement/OldIdeas
v8 v9 18 18 #!div style="background-color: #EEEEEE; border: 1px solid; margin: 20pt; padding: 5pt;" 19 19 '''brecht''': I don't like Waldemar's idea of having bundles spread all around the filesystem, hence the clear distinction between installed and non-installed bundles. This might be a necessity for multi-user too. 20 21 '''axeld''': I have to agree with brecht. And also, I like the package file system best, as it also solves on how to deal with ported software, and libraries as well. Only drivers would probably need special treatment (depends on how early the package file system is available, but I guess that could be made work as well, like having a "actually install on disk" option for driver packages). 20 22 }}} 21 23 … … 71 73 With assignfs, each port is mounted in its own directory: {{{/boot/apps/<port>-<version>-<revision>}}} 72 74 75 {{{ 76 #!div style="background-color: #EEEEEE; border: 1px solid; margin: 20pt; padding: 5pt;" 77 '''axeld''': I think the best solution would be a unionfs approach: the package file system would just blend in the packages where needed. User packages would be merged with the contents of config/, while system wide ones would be merged with the contents of /boot/common/.[[BR]] 78 Since we do care about binary compatibility, and stable APIs, having a central repository is not necessary, or something desirable at all IMO. 79 }}} 80 73 81 === Dependency Hell === 74 82 … … 99 107 100 108 Having an application use a particular library version can be done by manipulating LD_LIBRARY_PATH or by virtually placing the library in the applications directory by means of assignfs or pkgfs. 109 110 {{{ 111 #!div style="background-color: #EEEEEE; border: 1px solid; margin: 20pt; padding: 5pt;" 112 '''axeld''': while having a central repository is a good thing, I don't think our package manager should be based on that idea. I would allow each package to define its own sources (the user can prevent that, of course). That way, we avoid the situation of having to choose between outdated repositories, and unstable software (or even having to build it on your own) like you usually have to do in a Linux distribution. The central repository should also be a fallback, though, and try to host most library packages. 113 }}} 101 114 102 115 === libalpm ===