Licensing for ebuild

[flaviusb]

At present, the generated ebuilds seem to be licensed GPLv2 only, which seems to be incompatible with generating ebuilds for software licensed under the GPLv3.

[flaviusb]

This is relevant for me as I would like to package the packaging related things for all the distros I want to package for within the repo for the application I want to package ( https://github.com/flaviusb/pineapplepizza-rust-reference ), and the application is licensed under the GPLv3.

[cardoe]

So I’m trying to understand where the issue is. The LICENSE variable or the line at the top of the generated ebuild? Can you gist what it’s making for you?

[flaviusb]

Sorry, the line at the top of the generated ebuild is the issue, at least if distributing the ebuild along with the project counts as a bundled work. It might be that I am overthinking this.

Specifically, the lines:

# Copyright 2017-2018 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2

[flaviusb]

I am planning to put the debian related things in a debian subdirectory, and the gentoo related things in a gentoo subdirectory, and so forth.

[flaviusb]

If it is your understanding that including the generated ebuild within the applications repo would not constitute a combined work, or if you are willing to license the generated ebuild GPLv3 in addition to GPLv2, then my problem goes away.

[cardoe]

Change it as you want. It’s my opinion that a script outputted like that can it be copyrighted by a person. The only reason that is there is that repoman complains if it’s not in that exact format so I merged a PR to make it easier for people to create ebuilds to add to the tree.

[flaviusb]

Very cool. Thank you very much.