On Tue, 07 May 2013, Guillem Jover wrote: > > ;) well -- as I have mentioned, it is a non-free package (not even in > > Debian's non-free yet) which provides pre-built binary blobs > > (extensions), which on their own are redistributable, but that library > > is not. So it is upstream who builds/links against them -- I was just > > wrapping them into a convenience non-free package.
> Hmm, ok I see. This means installing the package will not produce a > working program, I've to question the point of packaging this at all? > Why not an installer-style package instead? installer-style package for the package in question would not resolve any problem -- that was the point of the exercise to take advantage of dpkg-shlibdeps to collect dependencies. Installer package for the library leading to error might be unfeasible (e.g. commercial-for-money and N/A while building the package). > > > generating pretty broken packages, for no apparent good reason. Given > > > this I'm inclined to close the bug report if no convincing > > > counter-arguments are put forward. > > I agree that it might lead to completely broken packages and generally > > should not be used. But in some cases (like mine) for non-free packages > > I see this option being useful. > Yes, it kind of “makes sense” it that case, but I'm not sure I'm happy > supporting that case (see the above question). I'm open to further > pondering about it though. and I understand your hesitance -- such use-cases are rare, and not per se toward solidification of Debian infrastructure within available suites (i.e. main/contrib/non-free). This might come useful though for internal/commercial use-cases like the one I have at hands. -- 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]
