Hello,
I've noticed in 1.4.0 the presence of doc/conda-recipes dir; from what
I got from the doc it's a build system for Anaconda Continuum systems.
May I ask what is the purpose of this directory? if it's for building,
why is it in the doc subtree?
Thanks in advance,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
Hello,
I've noticed in 1.4.0 the presence of doc/conda-recipes dir; from what
I got from the doc it's a build system for Anaconda Continuum systems.
yes conda is that -- but it's also open-source and can be used outside of
Anaconda. I think it makes a lot of sense to have a conda recipe in with
the package source.
May I ask what is the purpose of this directory? if it's for building,
why is it in the doc subtree?
I'm going to guess because it isn't (or wasn't) and "official" way to build
MPL. but I think it should probably go in the main source dir, alongside
setup.py -- conda is being pretty widely used these days.
-Chris
On Thu, Sep 11, 2014 at 1:07 PM, Sandro Tosi <morph@...12...> wrote:
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chris.Barker@...236...
Nothing against it, but have you checked the dir I mentioned? it's in
doc and it seems to contain build scripts for ~500 projects, maybe a
bit too much? 
Regards,
On Mon, Sep 15, 2014 at 5:33 PM, Chris Barker <chris.barker@...236...> wrote:
On Thu, Sep 11, 2014 at 1:07 PM, Sandro Tosi <morph@...12...> wrote:
Hello,
I've noticed in 1.4.0 the presence of doc/conda-recipes dir; from what
I got from the doc it's a build system for Anaconda Continuum systems.yes conda is that -- but it's also open-source and can be used outside of
Anaconda. I think it makes a lot of sense to have a conda recipe in with the
package source.May I ask what is the purpose of this directory? if it's for building,
why is it in the doc subtree?
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
I appaerently goofed when making the tarball and did not run enough
`git cleans` (or something?).
If they are in the tarball, that is my mistake (and they should not
be). I am hesitant to change the tarball on SF now as there maybe
people validating on that hash, but please remove those files when
building for debian.
I will make sure that the files for 1.4.1 (end of the month) are clean.
Tom
On Mon, Sep 15, 2014 at 3:46 PM, Sandro Tosi <morph@...12...> wrote:
On Mon, Sep 15, 2014 at 5:33 PM, Chris Barker <chris.barker@...236...> wrote:
On Thu, Sep 11, 2014 at 1:07 PM, Sandro Tosi <morph@...12...> wrote:
Hello,
I've noticed in 1.4.0 the presence of doc/conda-recipes dir; from what
I got from the doc it's a build system for Anaconda Continuum systems.yes conda is that -- but it's also open-source and can be used outside of
Anaconda. I think it makes a lot of sense to have a conda recipe in with the
package source.May I ask what is the purpose of this directory? if it's for building,
why is it in the doc subtree?Nothing against it, but have you checked the dir I mentioned? it's in
doc and it seems to contain build scripts for ~500 projects, maybe a
bit too much?Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
matplotlib-devel List Signup and Options
--
Thomas Caswell
tcaswell@...149...
I appaerently goofed when making the tarball and did not run enough
`git cleans` (or something?).If they are in the tarball, that is my mistake (and they should not
be). I am hesitant to change the tarball on SF now as there maybe
people validating on that hash,
yeah I would advise against modify a released tarball; once published,
it's there, you cant change it, just release a new version 
but please remove those files when
building for debian.
ah as I was saying, they are harmless, I was just wondering what such
a big directories tree is doing in the doc directory
I will make sure that the files for 1.4.1 (end of the month) are clean.
Cool, thanks!
On Mon, Sep 15, 2014 at 10:19 PM, Thomas Caswell <tcaswell@...149...> wrote:
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi