On Thu, May 12, 2011 at 5:29 AM, Maarten Derickx <m.derickx.stud...@gmail.com> wrote: [...] >> >> What would be the advantage of having it in the SPKG itself? >> > That it wil be compatible with parallel building as mentioned earlier. > >> Like if you want to install two packages that overwrite the same file? > I don't think we should never do (or even want) such a thing. I think > every spkg should only touch it's own files (or else we will get into > an unpredictable mess if we also want uninstall and parallel > building), if you really want an spkg to touch a file created by for > example foo.spkg, one should instead make a patch for the foo.spkg. > Maybe we should add some code that checks if there are spkg's breaking > this rule.
Definitely, two packages should not override the same files. So what you have in mind is: * automatically generate the list of files from *sequential* builds, store it in spkg (or possibly somewhere else) * use this in all default builds (either parallel or sequential), Sage would store the list of files somewhere, and use it for uninstall Is that right? Ondrej -- 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
