On Sun, Jan 03, 2010 at 10:34:12PM -0600, David Farning wrote:
The difference is that they expect to be able to install bundles via install_activity_bundle. From a technical POV the issue seems similar to how how Debian handles mozilla add ons. There are instances where users will want the ability to use and install addons, without being limited by their underlying distribution choice.
Seems equal to my "User B" (even emphasized by installing parts of the Sugar environment through .xo bundles).
If not, please elaborate.
The solution seem to be to create a meta package which (1) pulls in the dependencies sacha mentioned and (2) recommends a collection of activities. If a user/deployer prefers to install activities via install_activity_bundle they can install the meta package containing the dependencies without the activities themselves. Then they can install things via ASLO.
Do you mean some other package than my proposed honey-NN?
Either way, while this may be a huge philosophical difference, technically it should be straight forward. Go a head and package according to debian standards and expectations. We can add a couple of changes downstream for handling ALSO installs. If and when those changes prove useful, we can talk about pushing them into Debian.
What downstream hacks do you have in mind? Is it not currently working to install .xo bundles in Debian, or am I missing the point?
Kind regards, - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: Digital signature
