Suppose I write some package manager which will install, manage (start, stop, send commands, write configuration files etc.) binary programs distributed under various GPL licenses but not incorporate in my distribution. Can I license package manager under my own license of choice?
-
1Where does this package management tool of yours get the software it's going to install? Are you also running some kind of repository publishing software correctly formatted to install with Urusai_na's Package Manager? Or are you proposing a generic Windows-style installer, which is less of a package manager and more of a standard-format install script that ships with each piece of software it intends to install?– MadHatter ♦Oct 13, 2019 at 7:17
-
it's more like tool which use installation templates to download sources or binary forms from github and and other sources install it using apt-get or other native package manger depending of user preferences– urusai_naOct 13, 2019 at 7:57
1 Answer
You propose to write a piece of glueware which on one end is designed to interface with a variety of standard free software publishing sites (github, gitlab, sourceforge, etc.) and download software from them, internally refactor it, then present it on the other end to the user's standard system software installer (apt, yum, dnf, etc.). You want to know if the licensing of your glueware will be affected by the software it installs.
Basically, no, I believe it will not. Taking a Red Hat distro as an example, yum
is licensed under GPLv2, but is used to install software with many licenses, including software under other versions of the GPL, under non-copyleft free licences, and proprietary software. More generally, the licence of a program doesn't bleed to either its inputs or outputs, so one could similarly have a proprietary installer which installed free software. As long as you are not conveying free software, but merely providing code which allows the end-user to convey it to him or herself, then I don't immediately anticipate problems.