Hi, I've noticed we're getting more and more packages that has closed source licenses on the packaging itself. This is problematic as technically, we don't have rights to build those packages within MeeGo and probably even publish the source rpms on repo.meego.com and others to mirror our repos.
I don't know what the policy should be - frankly, I'd either prefer 'no license' like most of our spec files, or a general statement that our packaging (not content) is open source. Could distribution engineers/architects elaborate on this topic and set forth a policy? BR Carsten Munk _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
