Re: [Helidelinux-devel] Package manager
Status: Abandoned
Brought to you by:
rveen
From: Hui Z. <zh...@wa...> - 2004-03-16 20:45:30
|
On Tue, Mar 16, 2004 at 08:32:10PM +0000, Bennett Todd wrote: > I'm planning on tackling it when I add dependency management to bpm, > by ensuring that the build script fragment is run under something > like "strace -f -eexecve -efile" or thereabouts, and including build > dependancies on every package containing any file referenced in the > strace output. The result won't be true build dependancies (which I > can't think of any way of robustly automating); e.g. a lot of > packages on my build system will come up with dependencies against > coreutils and bash, that would be satisfied as well by Busybox. > Instead, the dependancies I'll compute will (a) document _exactly_ > how the package was built, for reproduceability, and (b) be useful > for offering suggestions about what might help if a rebuild attempt > fails. I am thinking that some dependency such as bash and libc are just so coomon, is it worth listing them at all. Here is an idea: always bundle some essential packages together and offer as a base system, thus many packages' dependency may automatically be solved. One may prepare a few different flavored base packages so user have choices. The base packages also can't be uninstalled but upgraded. -Hui Zhou |