excellent stuff! Michael Homer wrote: >> Did we try implementing it? I anticipate unexpected >> lacks-of-functionality in various alien package managers (though we can >> probably ask upstream to implement some of the accidentally-missing >> functionality when it's not too hard) > There may be some of that. I've tried to make the absolute > requirements as low as possible, and anything additional an optional > extra, so the only real requirement is being able to answer "do you > have X installed? Install it then". Hopefully they all provide at > least that.
let's see; Non-essential functionality: The user may want to list what packages are installed, or to uninstall some of them. I wonder what about multiple versions of alien packages? That could actually get quite messy (can it have multiple versions at once? How do you depend on a specific version of an alien package? What happens when the language's package collection changes and becomes newer and different over time? If multiple versions of an alien package are installed, and they can depend on different versions of others from that language, which are chosen (probably the external manager has good enough heuristics for this already.)? What about when alien packages depend on main packages (such as GTK+. Including header files.), both when you say "I want to install this Python package that depends on GTK+" and then later, when you upgrade GTK+ (this matters more for packages with unstable ABI)? so, er, I assume some of those concerns are unimportant but some of them might cause issues sometimes if left un-addressed, I was just brainstorming. -Isaac _______________________________________________ gobolinux-devel mailing list gobolinux-devel@lists.gobolinux.org http://lists.gobolinux.org/mailman/listinfo/gobolinux-devel
