On 2013-06-17, Volker Braun <vbraun.n...@gmail.com> wrote: > ------=_Part_3022_16440786.1371499844732 > Content-Type: text/plain; charset=ISO-8859-1 > > Will cygwin accept a monolithic Sage package that duplicates lots of Cygwin > packages? This is the same question about including Sage into linux > distros, and the answer is going to be a resounding "of course not".
cygwin allows for custom packages just as, say, Debian allows creating non-standard .deb files. That's what I keep in mind. http://sourceware.org/cygwin-apps/package-server.html Certainly, getting Sage into cygwin proper is much harder. > Of course it would be great to make Sage more modular, but its not going to > happen in the next few months. Packaging things correctly is the long-terms > solution, but for now we should just drop off a cygwin binary build > essentially the same way as we make the other binary builds. well, Cygwin is entangled with OS in an intimate way, so it's not "essentially the same way". Proper packaging of binary Windoze components is a bit of a dark art, and it's certainly harder than just vomit ;-) Yes, in fact, you can probably avoid using Cygwin installer, and use something else, creating a .cab file, or something like this. But it's more than just tar, and means reinventing the cygwin wheel. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/groups/opt_out.
