Mailinglist Archive: opensuse-packaging (145 mails)
| < Previous | Next > |
Re: [opensuse-packaging] Building packages with linking a license from licenses.rpm
- From: Reinhard Max <max@xxxxxxx>
- Date: Tue, 24 Jul 2007 18:31:17 +0200 (CEST)
- Message-id: <Pine.LNX.4.64.0707241824510.18011@xxxxxxxxxxxxxx>
On Tue, 24 Jul 2007 at 17:53, Michael Schroeder wrote:
> Oh, sorry, no it doesn't do that in names. (But I wouldn't do it in
> names, "Provide: licensemd5 = md5sum" is cleaner. See the kernel
> provides.)
What about using the full path names for the symbolic dependencies?
Using only the md5sum still has the risc of ending up with dangling
symlinks in case the licenses package ever reorganises it's directory
structure.
BTW, how does the license package approach fit with licenses that
require that the license text be included in any binary distribution?
As packages can be downloaded and installed without also downloading
the licenses package, people could view this as a license violation.
cu
Reinhard
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
> Oh, sorry, no it doesn't do that in names. (But I wouldn't do it in
> names, "Provide: licensemd5 = md5sum" is cleaner. See the kernel
> provides.)
What about using the full path names for the symbolic dependencies?
Using only the md5sum still has the risc of ending up with dangling
symlinks in case the licenses package ever reorganises it's directory
structure.
BTW, how does the license package approach fit with licenses that
require that the license text be included in any binary distribution?
As packages can be downloaded and installed without also downloading
the licenses package, people could view this as a license violation.
cu
Reinhard
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
| < Previous | Next > |