On May 14, 2012, at 7:47 AM, Julien Puydt wrote: > Le lundi 14 mai, Keshav Kini a écrit: >> A better solution, IMO, is to make scripts check the actual contents >> of the SPKG for extraneous directories and files. There should be no >> directories other than src/ and patches/ ; the line "src/" should be >> in .hgignore (which should exist), spkg-install should exist, SPKG.txt >> should exist, etc. Anything unknown in the root directory of the SPKG >> should generate a warning. > > Debian has an utility called 'lintian' which is a 'Static analysis tool > for Debian packages', and which checks that the package satisfies a > precise set of properties. No package goes in if it makes lintian > unhappy. > > Either sage would need such, or it should just put things right > (upstream tarballs in a directory -- building scripts in another > directory, under proper revision control).
When you build an spkg it already checks a few things. It shouldn't be hard to add other checks. Currently the checks are not "enforced" in the sense that they just print warnings, but don't change the return status or anything. This is in SAGE_ROOT/local/bin/sage-pkg if anyone wants to look at it. For example we could exclude repository data in the src/ directory of all spkgs. Deciding whether or not this is desirable is the hard part. There could even be an environment variable (since we all love them) specifying in the spkg-install which other files to exclude. -Ivan -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
