[opensuse-packaging] How to EULA in RPM package in OBS ?

older
[opensuse-packaging] virtualbox...

Pascal Bleser

25 Dec 2010 25 Dec '10

22:45

How can I make a package include an EULA message in the OBS ? I checked the flash-player package in the non-free repository but it has no apparent magic in it. (and it's nowhere on the wiki either) cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- I took the green pill _\_v FOSDEM XI: 5 + 6 Feb 2011, http://fosdem.org

Attachments:

attachment.sig (application/pgp-signature — 190 bytes)

Show replies by date

Mathias Homann

26 Dec 26 Dec

13:37

Am Samstag 25 Dezember 2010 schrieb Pascal Bleser:

...

How can I make a package include an EULA message in the OBS ? I checked the flash-player package in the non-free repository but it has no apparent magic in it. (and it's nowhere on the wiki either)

cheers I asked the same question on the obs mailing list quite some time ago, and it seems that that feature is not publicly available outside of opensuse itself. :/

bye, MH -- gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Marcus Meissner

13:47

On Sun, Dec 26, 2010 at 02:37:46PM +0100, Mathias Homann wrote:

...

Am Samstag 25 Dezember 2010 schrieb Pascal Bleser:

...
How can I make a package include an EULA message in the OBS ? I checked the flash-player package in the non-free repository but it has no apparent magic in it. (and it's nowhere on the wiki either)

cheers I asked the same question on the obs mailing list quite some time ago, and it seems that that feature is not publicly available outside of opensuse itself. :/

It is generated in primary.xml.gz to my knowledge, and so currently not possible externally. within the suse:license-to-confirm XML tag. See the update repos for the sample. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Pascal Bleser

14:43

On 2010-12-26 14:47:14 (+0100), Marcus Meissner wrote:

...

On Sun, Dec 26, 2010 at 02:37:46PM +0100, Mathias Homann wrote:

...
Am Samstag 25 Dezember 2010 schrieb Pascal Bleser:

...
How can I make a package include an EULA message in the OBS ? I checked the flash-player package in the non-free repository but it has no apparent magic in it. (and it's nowhere on the wiki either)

cheers I asked the same question on the obs mailing list quite some time ago, and it seems that that feature is not publicly available outside of opensuse itself. :/

It is generated in primary.xml.gz to my knowledge, and so currently not possible externally.

within the suse:license-to-confirm XML tag. See the update repos for the sample.

Hmmm, ok, thanks. So it's not possible to do it from OBS packages directly. Thing is, I've got a funky package here which is GPLv3 but also has an EULA (that one has to agree on before downloading the sources): http://pastie.org/1406533 Hm, I guess I'll cat the license agreement text from %post then, with something like "I you do not agree, remove this package". I'll try to find someone to talk to at Canon to clarify. cheers -- -o) Pascal Bleser /\\ http://opensuse.org -- I took the green pill _\_v FOSDEM XI: 5 + 6 Feb 2011, http://fosdem.org

Juergen Weigert

17:00

On Dec 26, 10 15:43:42 +0100, Pascal Bleser wrote:

...

On 2010-12-26 14:47:14 (+0100), Marcus Meissner wrote:

...
On Sun, Dec 26, 2010 at 02:37:46PM +0100, Mathias Homann wrote:

...
Am Samstag 25 Dezember 2010 schrieb Pascal Bleser:

...
How can I make a package include an EULA message in the OBS ? I checked the flash-player package in the non-free repository but it has no apparent magic in it. (and it's nowhere on the wiki either)

This feature was implemented in the suse internal PDB. I am not aware if it was ported to the BuildService.

...

...
It is generated in primary.xml.gz to my knowledge, and so currently not possible externally.

within the suse:license-to-confirm XML tag. See the update repos for the sample.

Hmmm, ok, thanks. So it's not possible to do it from OBS packages directly.

How should this be implemented in the BS? An entry in a ymp file or something?

...

Thing is, I've got a funky package here which is GPLv3 but also has an EULA (that one has to agree on before downloading the sources): http://pastie.org/1406533

That does not look sane: "2. RESTRICTIONS Except as expressly granted or permitted herein, you shall not use, assign, sublicense, sell, rent, lease, loan, convey or transfer to any third party the Software." This appears incompatible with GPLv3, unless Canon indicates that such language is overruled by the GPL. Further down it names 'Canon Bubble Jet Print Filter .. for Linux' and says: Such software modules are free software and you can redistribute them and/or modify them under the terms of GNU General Public License Version 2 published by the Free Software Foundation ("GPL"). Note that this language has no 'or later' options, thus again incompatible with GPLv3.

...

Hm, I guess I'll cat the license agreement text from %post then, with something like "I you do not agree, remove this package".

That would technically do, I guess. "7. TERM This Agreement is effective upon your acceptance hereof by using the Software ...." I still advise against cating an EULA in %post. We have no way to confirm that an end-user ever saw that EULA. Nobody can be bound to an EULA that he never saw. A dialog from a startup script would be much more effective.

...

I'll try to find someone to talk to at Canon to clarify.

Please do so. And please confirm with Canon if this EULA is meant to be GPLv3-compatible or not. Please also verify, if source-code is made available for the commands and libraries mentioned in the Appendix. My friendliest interpretation of the EULA is: (Nothing in the EULA is meant to contradict the GPL, thus) GPLv2 with linking exception Merry Christmas, Pascal! cheers, JW- -- o \ Juergen Weigert paint it green! __/ _=======.=======_ <V> | jw@suse.de back to ascii! __/ _---|____________\/ \ | 0911 74053-508 __/ (____/ /\ (/) | _____________________________/ _/ \_ vim:set sw=2 wm=8 SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) SuSE. Supporting Linux since 1992. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Pascal Bleser

17:54

On 2010-12-26 18:00:43 (+0100), Juergen Weigert wrote:

...

On Dec 26, 10 15:43:42 +0100, Pascal Bleser wrote:

...
On 2010-12-26 14:47:14 (+0100), Marcus Meissner wrote: [...]

...
suse:license-to-confirm XML tag. See the update repos for the sample.

Hmmm, ok, thanks. So it's not possible to do it from OBS packages directly.

How should this be implemented in the BS? An entry in a ymp file or something?

Most comfortable would be by convention: a file name in the (OBS) package with a specific name, something like "_EULA.txt", which would be auto-detected by OBS when generating the repository metadata.

...

...
Thing is, I've got a funky package here which is GPLv3 but also has an EULA (that one has to agree on before downloading the sources): http://pastie.org/1406533

That does not look sane: "2. RESTRICTIONS Except as expressly granted or permitted herein, you shall not use, assign, sublicense, sell, rent, lease, loan, convey or transfer to any third party the Software." This appears incompatible with GPLv3, unless Canon indicates that such language is overruled by the GPL.

Yeah, I'm a bit puzzled too.

...

Further down it names 'Canon Bubble Jet Print Filter .. for Linux' and says: Such software modules are free software and you can redistribute them and/or modify them under the terms of GNU General Public License Version 2 published by the Free Software Foundation ("GPL").

Note that this language has no 'or later' options, thus again incompatible with GPLv3.

Ah, true, I didn't spot that one.

...

...
Hm, I guess I'll cat the license agreement text from %post then, with something like "I you do not agree, remove this package".

That would technically do, I guess. "7. TERM This Agreement is effective upon your acceptance hereof by using the Software ...."

I still advise against cating an EULA in %post. We have no way to confirm that an end-user ever saw that EULA. Nobody can be bound to an EULA that he never saw.

That's a good point, indeed...

...

A dialog from a startup script would be much more effective.

As they're CUPS printer drivers, there is no startup script :\

...

...
I'll try to find someone to talk to at Canon to clarify.

Please do so. And please confirm with Canon if this EULA is meant to be GPLv3-compatible or not. Please also verify, if source-code is made available for the commands and libraries mentioned in the Appendix.

My friendliest interpretation of the EULA is: (Nothing in the EULA is meant to contradict the GPL, thus) GPLv2 with linking exception

Okay. And if not, I'll try to clarify whether redistribution would still be OK, might be something for non-free.

...

Merry Christmas, Pascal!

Thanks, to you too, and a happy new year :) (and thanks for having a look at the license :)) -- -o) Pascal Bleser /\\ http://opensuse.org -- I took the green pill _\_v FOSDEM XI: 5 + 6 Feb 2011, http://fosdem.org

Mathias Homann

18:27

How about this approach: - package a txt file with your software containing the license in question (you should contain such a file anyways, it could install into %docdir/%packagename) - write a small script that displays the license and asks for a Y/N - call that script from %pre the script could later be used in an obs macro so that you would simply call %_confirm_license licensefilename from %pre bye, MH Am Sonntag 26 Dezember 2010 schrieb Pascal Bleser:

...

On 2010-12-26 18:00:43 (+0100), Juergen Weigert wrote:

...
On Dec 26, 10 15:43:42 +0100, Pascal Bleser wrote:

...
On 2010-12-26 14:47:14 (+0100), Marcus Meissner wrote: [...]

...
...
...
suse:license-to-confirm

XML tag. See the update repos for the sample.

Hmmm, ok, thanks. So it's not possible to do it from OBS packages directly.

How should this be implemented in the BS? An entry in a ymp file or something?

Most comfortable would be by convention: a file name in the (OBS) package with a specific name, something like "_EULA.txt", which would be auto-detected by OBS when generating the repository metadata.

...
...
Thing is, I've got a funky package here which is GPLv3 but also has an EULA (that one has to agree on before downloading the sources): http://pastie.org/1406533

That does not look sane: "2. RESTRICTIONS Except as expressly granted or permitted herein, you shall not use, assign, sublicense, sell, rent, lease, loan, convey or transfer to any third party the Software."

This appears incompatible with GPLv3, unless Canon indicates that such language is overruled by the GPL.

Yeah, I'm a bit puzzled too.

...
Further down it names 'Canon Bubble Jet Print Filter .. for Linux' and

says: Such software modules are free software and you can redistribute them and/or modify them under the terms of GNU General Public License Version 2 published by the Free Software Foundation ("GPL").

Note that this language has no 'or later' options, thus again incompatible with GPLv3.

Ah, true, I didn't spot that one.

...
...
Hm, I guess I'll cat the license agreement text from %post then, with something like "I you do not agree, remove this package".

That would technically do, I guess.

"7. TERM

This Agreement is effective upon your acceptance hereof by using the Software ...."

I still advise against cating an EULA in %post. We have no way to confirm that an end-user ever saw that EULA. Nobody can be bound to an EULA that he never saw.

That's a good point, indeed...

...
A dialog from a startup script would be much more effective.

As they're CUPS printer drivers, there is no startup script :\

...
...
I'll try to find someone to talk to at Canon to clarify.

Please do so. And please confirm with Canon if this EULA is meant to be GPLv3-compatible or not. Please also verify, if source-code is made available for the commands and libraries mentioned in the Appendix.

My friendliest interpretation of the EULA is: (Nothing in the EULA is meant to contradict the GPL, thus) GPLv2 with linking exception

Okay. And if not, I'll try to clarify whether redistribution would still be OK, might be something for non-free.

...
Merry Christmas, Pascal!

Thanks, to you too, and a happy new year :) (and thanks for having a look at the license :))

-- gpg key fingerprint: 5F64 4C92 9B77 DE37 D184 C5F9 B013 44E7 27BD 763C -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Marcus Meissner

21:44

On Sun, Dec 26, 2010 at 07:27:16PM +0100, Mathias Homann wrote:

...

How about this approach:

- package a txt file with your software containing the license in question (you should contain such a file anyways, it could install into %docdir/%packagename) - write a small script that displays the license and asks for a Y/N - call that script from %pre

the script could later be used in an obs macro so that you would simply call %_confirm_license licensefilename from %pre

In general software built in the OBS itself should not require an EULA at all, as only Opensource software should be built there. The rest is a feature request I gues. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

Ladislav Slezak

29 Dec 29 Dec

11:32

Dne 26.12.2010 19:27, Mathias Homann napsal(a):

...

How about this approach:

- package a txt file with your software containing the license in question (you should contain such a file anyways, it could install into %docdir/%packagename) - write a small script that displays the license and asks for a Y/N - call that script from %pre

the script could later be used in an obs macro so that you would simply call %_confirm_license licensefilename from %pre

Um, no. Please don't use any interactive scripts in any RPM scripts like %pre or %post. That would work when using plain 'rpm' command for installation, but would break when using YaST (no console output in GUI!) or an automatic installation. And zypper has option '--auto-agree-with-licenses' which also wouldn’t work correctly with custom scripts... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

4877

Age (days ago)

4881

Last active (days ago)

List overview

Download

8 comments

5 participants

participants (5)

Juergen Weigert
Ladislav Slezak
Marcus Meissner
Mathias Homann
Pascal Bleser