I like this idea but it provides another layer of complexity. What if someone simply forgets to add a license subdirectory? Does that make their package invalid or does sage -i foo.spkg fail?
In the case of gap_packages*, a number of Gap packages are bundled, with varying licenses (mostly GPL but nauty is there too). The maintainer (me, I guess) would have to add all these individual license files together into a single license subdirectory? ++++++++++++++++++++++++++++++++++++++ On Mon, Sep 8, 2008 at 4:00 PM, Georg S. Weber <[EMAIL PROTECTED]> wrote: > > Hi Sage-Devel, > > What do you think of adding a license/ subdirectory to each spkg? > When the spkg, say foo-1.2.3.spkg is installed, the directory > > SAGE_ROOT/license/packages/foo > > would be a copy of that license/ subdirectory. > > (The above is shamelessly copied from the start of Williams "doc/" > proposal and only slightly modified ...) > There are several reasons for this new proposal: > > 1. The original proposal about doc/ was received positively. > 2. I have optional and experimental spgks in my mind, which are not > covered by the current one big "license" file for the standard sage. > But Sage is designed and made for ease of plugging new spkgs in. Which > have to be developed. > 3. Any move to a more modular structure like this increases > maintainability. If this proposal receives a positive feedback, my > next proposal in this direction would be to "modularize" the license > information for the "standard" Sage, too. (Not to mention > "SageLite" ...) And I'd volunteer to do this :-) > 4. Should we end up with 75 or even more than 100 copies of the GPL > --- who really cares? These are text files with uncompressed only a > very few KB, so are sizewise negligible (for downloads e.g.), > especially after bz2-ing. > 5. For convenience, one might go one step further and have an > additional "short version" of the license information in each spgk's > license/ subdirectory, and the build process compile those together to > a single "overview" file ... a slicing up of the current file being a > good starting point. > > I see only pro's but no con's. Am I missing something? > > > Cheers, > gsw > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
