Hi > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Carsten Munk > Sent: Monday, November 22, 2010 3:42 PM > To: [email protected] > Subject: [meego-packaging] Licensing on spec files > > 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. > Give an example
> 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. > What do you mean by "no license"? > 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 _______________________________________________ MeeGo-packaging mailing list [email protected] http://lists.meego.com/listinfo/meego-packaging
