The full text of all licenses in the code need to be in the copyright file.
Copyright statements should also be listed, at the top. Tying Copyright statements to license types, like is done here, is extra credit, at this point. The license type string should also contain the key licenses used, separated by commas (ie. BSD,GPLv2 etc...). Cheers, Jim Federico Beffa wrote: > Hi All, > > I'm working on the spec file for a package (netpbm) which provides > several small command-line applications. The applications are not all > licensed under the same conditions. In the review process of the spec > file people have suggested to only put a single license in the spec > file. However, in my opinion this is not correct and I would suggest to > keep all of the licenses. I checked out of curiosity what the Fedora > people do for the same package and they also put all of the licenses in > the license line of the spec file. > > In the past this topic has already been discussed, but with no clear > conclusion. Can we try to reach agreement with clear guidelines going > forward? > > Thanks, > Fede > > P.S.: here you can check the spec file: > http://jucr.opensolaris.org/review/packages/1200/ > > > ------------------------------------------------------------------------ > > _______________________________________________ > sw-porters-discuss mailing list > sw-porters-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/sw-porters-discuss -- Jim Walker, http://blogs.sun.com/jwalker Sun Microsystems, Broomfield, Colorado
