[mpir-devel] Re: Obsolete Symbols

2010-04-09 Thread Cactus
On Apr 9, 11:41 pm, Bill Hart wrote: > I posted a list of obsolete symbols on sage-devel and asked > maintainers to remove them from their packages. > > We've also permanently removed mpz_random and mpz_random2. > > I think we should remove one or two symbols per release and encourage > anyone w

Re: [mpir-devel] Obsolete Symbols

2010-04-09 Thread William Stein
On Fri, Apr 9, 2010 at 3:41 PM, Bill Hart wrote: > I posted a list of obsolete symbols on sage-devel and asked > maintainers to remove them from their packages. > > We've also permanently removed mpz_random and mpz_random2. > > I think we should remove one or two symbols per release and encourage

Re: [mpir-devel] Obsolete Symbols

2010-04-09 Thread Bill Hart
I posted a list of obsolete symbols on sage-devel and asked maintainers to remove them from their packages. We've also permanently removed mpz_random and mpz_random2. I think we should remove one or two symbols per release and encourage anyone who hasn't removed them already to do so. We just di

[mpir-devel] Obsolete Symbols

2010-04-09 Thread Cactus
It seems to me that we keep trying to remove obsolete GMP symbols from mpir.h only to find that we have to put them back in again. But if we put them back in, nobody then bothers to update their code to remove them. We hence need to do something that makes it evident that an obsolete symbol is in

Re: [mpir-devel] Re: MPIR Announcement

2010-04-09 Thread Bill Hart
Whoops, I nearly forgot. The svn had to be moved as we had problems at the original location. Here is the new address: http://boxen.math.washington.edu/svn/mpir/mpir/ Thanks again to William Stein for hosting this for us! Bill. On 9 April 2010 13:55, Bill Hart wrote: > On 9 April 2010 13:23

Re: [mpir-devel] Re: MPIR Announcement

2010-04-09 Thread Bill Hart
On 9 April 2010 13:23, Marc wrote: > Hello, > > I am not sure I understand what is going on with MPIR. When the fork > happened, 2 of the main stated goals where: > 1) LGPL2 (required for sage+microsoft) > --> MPIR is now LGPL3+ only Correct. Will this create any issues for you? > 2) a more open

[mpir-devel] Re: MPIR Announcement

2010-04-09 Thread Marc
Hello, I am not sure I understand what is going on with MPIR. When the fork happened, 2 of the main stated goals where: 1) LGPL2 (required for sage+microsoft) --> MPIR is now LGPL3+ only 2) a more open development process --> the public svn repository has been unavailable for months, the public ma