On Friday, December 2, 2016 at 10:06:34 AM UTC, Ralf Stephan wrote: > > On Friday, December 2, 2016 at 10:51:47 AM UTC+1, Han Frederic wrote: >> >> We had this argument already. If you prefer to keep it this way, please >>>> provide us a VCS (git preferred) repo >>>> off which we can label releases by the latest commit in the master >>>> branch, or something like this. >>>> This way at least meaningful bug reports can be filed. Please... >>>> We (or in fact any Linux/OSX distribution system) cannot work with >>>> different tarballs that are named the same, we do not have tools to >>>> support >>>> this. Each tarball change without name change triggers an alert screaming >>>> that it has been tampered with. >>>> >>> >> But the giac spkg is always built from these sources via the spkg-src: >> >> http://www-fourier.ujf-grenoble.fr/~parisse/debian/dists/stable/main/source/ >> and they have a meaningful name. Ex: spkg 1.2.2.103 is from source >> 1.2.2-103. >> > > I think numbering changes at level 4 are the problem that Dima (quote > above) meant. > None of the toolos support it. >
I was talking about silently changing a tarfile, without changing its name at all. -- 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 https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
