On Dec 31, 11:40 pm, "Ted Kosan" <[EMAIL PROTECTED]> wrote:
> Michael.wrote:
>
> > The documentation for each spkg can and will certainly be improved. We
> > should stuff that information in the developer's guide (like the
> > release manager guide I am currently writing, which will be added
> >
Michael.wrote:
> The documentation for each spkg can and will certainly be improved. We
> should stuff that information in the developer's guide (like the
> release manager guide I am currently writing, which will be added
> there at some point in time).
I think that having guidelines like this
On Dec 31, 2:15 am, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
Sorry for being late to the party, I was afk for a while.
> > When I look at the instructions for creating a spkg:
>
> >http://www.sagemath.org/doc/html/prog/node24.html
>
> > The first thing that catches my eye is
>
> > "(b)
> >
On Dec 31, 1:11 pm, "Ted Kosan" <[EMAIL PROTECTED]> wrote:
> Ondrej wrote:
> > Nice thing about this is that there is no database, nothing. Just
> > plain files, that
> > can be fixed by hand.
>
> > How would portage improve this?
>
> Portage is just editable text files too. I do not have any e
> When I look at the instructions for creating a spkg:
>
> http://www.sagemath.org/doc/html/prog/node24.html
>
> The first thing that catches my eye is
>
> "(b)
> Put your files in that directory."
>
> So where do the files come from? I took a spkg at random (readline),
Yes, for the sympy spk
Ondrej wrote:
> Nice thing about this is that there is no database, nothing. Just
> plain files, that
> can be fixed by hand.
>
> How would portage improve this?
Portage is just editable text files too. I do not have any experience
with Debian so it may also do the following things I describe be
On Dec 30, 2007 6:14 PM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> On Dec 30, 2007 11:58 PM, Francois <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > On Dec 31, 1:51 am, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
> > >
> > > Disclaimer: I am a Debian user, on the way of becoming a Debian Developer
>
On Dec 30, 2007 11:58 PM, Francois <[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 31, 1:51 am, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
> >
> > Disclaimer: I am a Debian user, on the way of becoming a Debian Developer
> >
> > I agree with Michael, to keep it simple stupid, as it is now. Maybe with my
On Dec 31, 1:51 am, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
>
> Disclaimer: I am a Debian user, on the way of becoming a Debian Developer
>
> I agree with Michael, to keep it simple stupid, as it is now. Maybe with my
> a simple improvements I suggested here:
>
> http://groups.google.com/grou
On Dec 29, 2007 8:04 AM, François Bissey <[EMAIL PROTECTED]> wrote:
>
> On Sat, 29 Dec 2007, mabshoff wrote:
> > Well, if we were to limit ourselves to Linux systems that might be an
> > option, but with the need to support OSX and Solaris [and in the
> > futute Windows] I don't see this as somethi
On Sat, 29 Dec 2007, mabshoff wrote:
> Well, if we were to limit ourselves to Linux systems that might be an
> option, but with the need to support OSX and Solaris [and in the
> futute Windows] I don't see this as something viable. Portage is nice,
> but it is the wrong tool for a cross platform t
On Dec 29, 7:33 am, "Ted Kosan" <[EMAIL PROTECTED]> wrote:
> Michael wrote:
> > Well, if we were to limit ourselves to Linux systems that might be an
> > option, but with the need to support OSX and Solaris [and in the
> > futute Windows] I don't see this as something viable. Portage is nice,
>
Michael wrote:
> Well, if we were to limit ourselves to Linux systems that might be an
> option, but with the need to support OSX and Solaris [and in the
> futute Windows] I don't see this as something viable. Portage is nice,
> but it is the wrong tool for a cross platform toolchain. What we
> c
On Dec 28, 2007 10:11 PM, mabshoff
<[EMAIL PROTECTED]> wrote:> we include
in case I am not already on the mailing list :). We should
> actually create something like that because if you do not read sage-
> devel or sage-support chances are you might miss some release. It is
> more and more my impr
On Dec 27, 9:18 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What *standard* Sage spkg packages are out of date right now
> (I'm skimminghttp://sagemath.org/components.html)?
>
> * cddlib: we ship 094b, but 094d is current.
#1619
> * clisp: we ship clisp-2.41, but 2.43 is current
On Dec 28, 2007, at 8:28 PM, mabshoff wrote:
>>
>> We need:
>> (a) a wiki page that lists packages with the corresponding
>> maintainer.
>> (b) A natural system for updating patches. I like your
>> suggestion above,
>> though _not_ the order.
>> (1) Create a trac ticke
On Dec 28, 8:38 pm, "William Stein" <[EMAIL PROTECTED]> wrote:
> On Dec 28, 2007 3:54 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
Hi,
since nobody has stepped up yet I am volunteering to do this. I can
certainly need some help and am more than willing to share those
duties. Since I do most
On Dec 29, 4:52 am, "Ted Kosan" <[EMAIL PROTECTED]> wrote:
> William wrote:
> > What should we do? Any ideas? People who work on Linux distributions,
> > please speak up, except for saying "don't bother with Sage, we already
> > package everything above in Debian"
>
> Since Gentoo is a meta L
William wrote:
> What should we do? Any ideas? People who work on Linux distributions,
> please speak up, except for saying "don't bother with Sage, we already
> package everything above in Debian"
Since Gentoo is a meta Linux distribution (a distribution which is
designed to build custom dis
On Dec 28, 2007 2:38 PM, William Stein <[EMAIL PROTECTED]> wrote:
>
> On Dec 28, 2007 3:54 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
> >
> > Are there some instructions for Sage package maintainers to follow?
> > I.e. what exact steps are neede to update the package?
>
> There are no instructio
On Dec 28, 2007 3:54 AM, Ondrej Certik <[EMAIL PROTECTED]> wrote:
>
> Are there some instructions for Sage package maintainers to follow?
> I.e. what exact steps are neede to update the package?
There are no instructions, and no master list of package maintainers, etc.
One of the goals of this th
On Dec 27, 2007 1:55 PM, mabshoff
<[EMAIL PROTECTED]> wrote:
>
>
>
> On Dec 27, 9:18 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > What *standard* Sage spkg packages are out of date right now
> > (I'm skimminghttp://sagemath.org/components.html)?
> >
> > * cddlib: we ship 094b, b
On Dec 27, 9:18 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What *standard* Sage spkg packages are out of date right now
> (I'm skimminghttp://sagemath.org/components.html)?
>
> * cddlib: we ship 094b, but 094d is current.
> * clisp: we ship clisp-2.41, but 2.43 is current (I'm
On Dec 27, 9:18 am, "William Stein" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> What *standard* Sage spkg packages are out of date right now
> (I'm skimminghttp://sagemath.org/components.html)?
>
> * cddlib: we ship 094b, but 094d is current.
> * clisp: we ship clisp-2.41, but 2.43 is current (I'm
24 matches
Mail list logo
