oki doki -- since it seems to be too quiet... let me start from an attacking angle: by using debian/upstream as the container for publication references we can't decouple separate components having different publication references to use for different components, neither shipped in separate binary packages or a single one (e.g. a collection of datasets).
The only viable resolution as far as I see it to extend Reference entry(ies) with e.g. "Files:" field which would contain a list of globs to point to files as installed on the system by binary packages. But that cross the line from upstream and source packages into the land of binary packages... not sure how you guys would accept it. Otherwise, without such specification, all the references are somewhat useless e.g. in cases when there are multiple for completely different components provided by any given source package. -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
