On Oct 31, 1:50 pm, "Ondrej Certik" <[EMAIL PROTECTED]> wrote:
> Hi,
Hello Ondrej,
>
> when I have one particular feature to discuss, should I discuss it
> here, or open a new trac ticket for that?
Something this controversial should be discussed here first. Either
way you should get a trac account via William, it can't hurt to have
one :)
>
> I am going to discuss it here for now:
>
> summary: infer the name of the spkg package from config file (instead
> of the name of the dir)
>
> Currently, when creating a package using
>
> ./sage -pkg some_dir
>
> will create a package
>
> "some_dir"
>
> which is inconvenient, because the some_dir is held in a hg
> repository, whose dir doesn't change. Also, all information about
> creating the package should be included in the hg repository. I
> suggest creating a file, changelog, that will hold the latest version.
> And also it will contain the info from SPKG.txt (this fill will could
> be removed then). Why not to do it the same as in Debian? Example of a
> Debian changelog:
>
> libmesh (0.6.1.dfsg-1~oc3) UNRELEASED; urgency=low
>
> [Ondrej Certik]
> * New upstream version
> * Ondrej Certik added to Uploaders.
>
> TODO before the package can be uploaded to Debian:
> * check lintian/linda
> * check that libmesh-pure works as expected
> * remove the "-j4" flags in make in debian/rules
>
> -- Ondrej Certik <[EMAIL PROTECTED]> Sun, 28 Oct 2007 17:45:28 +0100
>
> libmesh (0.6.0~rc2.dfsg-3) unstable; urgency=low
>
> [Ondrej Certik]
> * Built against libpetsc2.3.3, which is now in Debian (Closes: #435532)
>
> [ Christophe Prud'homme ]
> * debian/control: modified maintainer and uploader fields
>
> -- Christophe Prud'homme <[EMAIL PROTECTED]> Mon, 03 Sep 2007 22:11:32 +0200
>
> The building scripts in Debian parse the first line, and get the
> version information from that (in Debian it's a little more
> complicated, since there are source and binary packages, the names of
> which are read from the debian/control file). In SAGE, most of the
> things are not needed, so I suggest this syntax:
>
> sympy (0.5.6-2)
>
> [Ondrej Certik]
> * get-orig-sources added
>
> sympy (0.5.6-1)
>
> [Ondrej Certik]
> * New upstream version
> * file .hgignore added
>
> sympy (0.5.5-1)
>
> * New upstream version
>
> ...
>
> and spkg -pkg will parse the first line (and only the first line), and
> get the name of the package and version from that. The "-1", "-2" are
> SAGE revisions of the package - when you change something in the
> building of the package, but the upstream version doesn't change, so
> that it's reflected in the version.
>
We use .p1, .p2 and so on for that so far, but your suggestion works
just as fine.
> Ondrej
I would recommend you wait for some reactions until the east & west
coast crowd gets up; Then you should write a Sage Enhancement Proposal
and even better implement a prototype of your idea so people can play
around with it. If it breaks backward compability it would be a harder
sell, but it might be something to target for Sage 3.0 which should
happen in the not so distant future, i.e. roughly the start of 2008.
That said I like you ideas and suggestions. It should be possible to
add hash values for consistency which is something Pablo has been
working on (see #329), so you might want to talk to him about how this
can be combined.
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-devel@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/
-~----------~----~----~----~------~----~------~--~---
