On Fri, 5 May 2006, Thibaut Paumard wrote:
Actually, if I stay with the one-package-per-plugin approach, I was thinking of providing a virtual package that would pull out yorick and all the plugins (except perhaps the most specialised). Would that make sense? In that case, I also need to think of a reasonable versionning. (the above looks OK).
I think what you want is a meta package that pulls in all the components, The virtual package is a bit different.[0] You could have a meta package called yorick-standard-plugins or something like that which depends on yorick and the plugins you think are fundamental.
[0] http://www.debian.org/doc/debian-policy/ch-relationships.html Cheers, Carlo -- Carlo U. Segre -- Professor of Physics Associate Dean for Special Projects, Graduate College Illinois Institute of Technology Voice: 312.567.3498 Fax: 312.567.3494 [EMAIL PROTECTED] http://www.iit.edu/~segre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
