[sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
I'd say it's better to create a Legacy section and more this info there, as long as it is relevant... On Tuesday, 6 January 2015 07:11:24 UTC, Nathann Cohen wrote: Hello everybody ! There is in our developer's manual a section entitled Packaging Third-Party Code which contains two sections: - Packaging Third-Party Code - Packaging Old-Style SPKG ( see http://www.sagemath.org/doc/developer/#packaging-third-party-code ) The second part of it is about our former .spkg files, how to build them, the use of HG, etc... What would you think of removing it and only have the content of Packaging Third-party code in this section ? I would of course check that the info it contains (and that are still valid) also appear in the 'new spkg' section. Nathann -- 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/d/optout.
[sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
Hi Francois, On 2015-01-06, Francois Bissey francois.bis...@canterbury.ac.nz wrote: Are you meaning that you still update it as an “old” spkg? Yes. Reason? Hm. The best reason I have is this: The code in the spkg has never been published elsewhere, and thus I think that the spkg *is* upstream. Somebody told me that I should post the code somewhere on github. But then I think this would be an artificial complication. Moreover, I plan to migrate the code of the spkg to the Sage library; if this will be done, the optional spkg will only be useful to do cross-verifications of computations, and will not be further maintained. Seriously I thought Nathann was only talking about producing such a spkg. No, the spkg was produced long time ago. Best regards, Simon -- 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/d/optout.
Re: [sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
Hi, it could be nice to have a list of the non-migrated spkgs that are still needed. Depending on its size, working on a raw migration to get rid of the old-style spkgs will be a great simplification. As for me, i see: - cbc - nauty A side effect would be to easily fix the currently broken sage -optional and sage -standard commands, they currently lists old version found on the web while with a complete move to the new-style packaging it will suffice to look at the local build/pkgs directory. Ciao, Thierry On Tue, Jan 06, 2015 at 01:18:32PM +0530, Nathann Cohen wrote: Yo ! Reason: There still exist old style spkgs (I am to blame for one optional old style spkg), and as long as that is the case, information on their format is relevant. I was wondering about that, actually. If they are ever updated again, shouldn't they be converted to new style spkg ? It is a bit like the recent removal of the sagedev scripts documentation. While we keep the feature, I thought that we should stop advertising it. This being said, I hear and understand your objection: I asked the question in order to know what you thought of it, and if you do not like the idea the problem is settled :-) Have fun ! Nathann -- 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/d/optout. -- 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/d/optout.
Re: [sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
Well, that's two people already... Yepyep. For the time being perhaps one can change the wording to indicate only for legacy packages, we expect new packages to be in this format. I have to say that needing a patch for ''every'' upgrade of a pkg is annoying, sage -i should just work. Also, I do not know myself how anybody who would like to distribute his own Sage package could do it (with the new style) without having to create a patch. Sebastien mentionned the checksum problem, but HE knows how to contribute to Sage if he needs to. If one does not, isn't it impossible to create a new style package to just share code with some persons ? To sum it up - no patch to remove that doc. But this conversation raised some sensible issues. Nathann -- 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/d/optout.
[sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
Last August, I released the first version of my slabbe-0.1.spkg. I had to choose at that time between the old-style and the new style. I explained here [1] why I finally choose the old-style. If I use the new style and I release slabbe-0.2 tomorrow during a conference let say for fixing a bug found by a colleague, then the version 0.2 won't install on the sage installation of my colleague. Why? The checksums need to be updated. And, I want it to be a simple installation one liner like sage -i slabbe-0.2.spkg that anybody can do. That is why I believe that old style is still usefull for packages farther from sage (my package is not listed anywhere I think). [1] http://www.liafa.univ-paris-diderot.fr/~labbe/blogue/2014/08/releasing-slabbe-my-own-sage-package/ Of course maybe that issue can be fixed somehow in the new git system. A command like the following would make me happy: sage -i --forgetaboutchecksums slabbe-0.2.tar Sébastien On Tuesday, January 6, 2015 4:33:14 AM UTC-5, Simon King wrote: Hi Francois, On 2015-01-06, Francois Bissey francoi...@canterbury.ac.nz javascript: wrote: Are you meaning that you still update it as an “old” spkg? Yes. Reason? Hm. The best reason I have is this: The code in the spkg has never been published elsewhere, and thus I think that the spkg *is* upstream. Somebody told me that I should post the code somewhere on github. But then I think this would be an artificial complication. Moreover, I plan to migrate the code of the spkg to the Sage library; if this will be done, the optional spkg will only be useful to do cross-verifications of computations, and will not be further maintained. Seriously I thought Nathann was only talking about producing such a spkg. No, the spkg was produced long time ago. Best regards, Simon -- 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/d/optout.
[sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
Last August, I released the first version of my slabbe-0.1.spkg. I had to choose at that time between the old-style and the new style. I explained here [1] why I finally choose the old-style. If I use the new style and I release slabbe-0.2 tomorrow during a conference let say for fixing a bug found by a colleague, then the version 0.2 won't install on the sage installation of my colleague. Why? The checksums need to be updated. And, I want it to be a simple installation one liner like sage -i slabbe-0.2.spkg that anybody can do. That is why I believe that old style is still usefull for packages farther from sage (my package is not listed anywhere I think). Are you meaning that you still update it as an “old” spkg? Yes. Reason? Hm. The best reason I have is this: The code in the spkg has never been published elsewhere, and thus I think that the spkg *is* upstream. Somebody told me that I should post the code somewhere on github. But then I think this would be an artificial complication. Moreover, I plan to migrate the code of the spkg to the Sage library; if this will be done, the optional spkg will only be useful to do cross-verifications of computations, and will not be further maintained. Well, that's two people already... For the time being perhaps one can change the wording to indicate only for legacy packages, we expect new packages to be in this format. I have to say that needing a patch for ''every'' upgrade of a pkg is annoying, sage -i should just work. -- 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/d/optout.
[sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
Hi Karl-Dieter, On 2015-01-06, kcrisman kcris...@gmail.com wrote: I have to say that needing a patch for ''every'' upgrade of a pkg is annoying, sage -i should just work. Every upgrade should be reviewed. So, it must not be possible that a change in the upstream sources is automatically applied (I guess that's why spkgs have checksums) without a *reviewed* change (e.g., an update of the checksums) in Sage. However, it *should* be possible to explicitly do ./sage -i great_package-2.0.0.beta3 even if ./sage -i gread_package would install, say, version 1.2.1. Best regards, Simon -- 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/d/optout.
[sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
I have to say that needing a patch for ''every'' upgrade of a pkg is annoying, sage -i should just work. Every upgrade should be reviewed. So, it must not be possible that a Sorry, I meant that to upgrade an spkg the end user shouldn't have to do anything. change in the upstream sources is automatically applied (I guess that's why spkgs have checksums) without a *reviewed* change (e.g., an update of the checksums) in Sage. However, it *should* be possible to explicitly do ./sage -i great_package-2.0.0.beta3 even if ./sage -i gread_package would install, say, version 1.2.1. Best regards, Simon -- 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/d/optout.
Re: [sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
Yo ! Reason: There still exist old style spkgs (I am to blame for one optional old style spkg), and as long as that is the case, information on their format is relevant. I was wondering about that, actually. If they are ever updated again, shouldn't they be converted to new style spkg ? It is a bit like the recent removal of the sagedev scripts documentation. While we keep the feature, I thought that we should stop advertising it. This being said, I hear and understand your objection: I asked the question in order to know what you thought of it, and if you do not like the idea the problem is settled :-) Have fun ! Nathann -- 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/d/optout.
[sage-devel] Re: Should we remove Packaging Old-Style SPKG from the developer's manual ?
Hi all, On 2015-01-06, Francois Bissey francois.bis...@canterbury.ac.nz wrote: +1 to remove. On 6/01/2015, at 20:11, Nathann Cohen nathann.co...@gmail.com wrote: The second part of it is about our former .spkg files, how to build them, the use of HG, etc... What would you think of removing it and only have the content of Packaging Third-party code in this section ? I would of course check that the info it contains (and that are still valid) also appear in the 'new spkg' section. I'd vote against removing it. Reason: There still exist old style spkgs (I am to blame for one optional old style spkg), and as long as that is the case, information on their format is relevant. That said, if my spkg is the *only* old style spkg, then I should better soon open a ticket to make it new style. Best regards, Simon -- 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/d/optout.
