Discussion:
[Numpy-discussion] numpy vendor repo
Ralf Gommers
10 years ago
Permalink
Hi,

Today I wanted to add something to https://github.com/numpy/vendor and
realised that this repo is in pretty bad shape. A couple of years ago
Ondrej took a copy of the ATLAS binaries in that repo and started a new
repo (not a fork) at https://github.com/certik/numpy-vendor. The latest
improvements were made by Julian and live at
https://github.com/juliantaylor/numpy-vendor.

I'd like to start from numpy/vendor, then add all commits from Julian's
numpy-vendor on top of it, then move things around so we have the
binaries/sources/tools layout back and finally update the README so it's
clear how to build both the ATLAS binaries and Numpy releases.

Any objections or better ideas?

Ralf
Charles R Harris
10 years ago
Permalink
...
No objections from me, getting all the good stuff together in an easily
found place is a plus.

Chuck
Ralf Gommers
10 years ago
Permalink
...
Done in the master branch of https://github.com/rgommers/vendor. I think
that "numpy-vendor" is a better repo name than "vendor" (which is pretty
much meaningless outside of the numpy github org), so I propose to push my
master branch to https://github.com/numpy/numpy-vendor and remove the
current https://github.com/numpy/vendor repo.

I'll do this in a couple of days, unless there are objections by then.

Ralf
David Cournapeau
10 years ago
Permalink
...
As the original creator of vendor, I am +1 on this as well !

David
Ralf
_______________________________________________
NumPy-Discussion mailing list
http://mail.scipy.org/mailman/listinfo/numpy-discussion
Peter Cock
10 years ago
Permalink
Post by Ralf Gommers
Done in the master branch of https://github.com/rgommers/vendor. I think
that "numpy-vendor" is a better repo name than "vendor" (which is pretty
much meaningless outside of the numpy github org), so I propose to push my
master branch to https://github.com/numpy/numpy-vendor and remove the
current https://github.com/numpy/vendor repo.
I'll do this in a couple of days, unless there are objections by then.
Ralf
Can you not just rename the repository on GitHub?

Peter
Ralf Gommers
10 years ago
Permalink
...
Yes, that is possible. The difference is small in this case (retaining the
1 closed PR fixing a typo; there are no issues), but after looking it up I
think renaming is a bit less work than creating a new repo. So I'll rename.

Ralf
Ralf Gommers
10 years ago
Permalink
...
This is done now.

If anyone wants to give it a try, the instructions in README.txt should
work for producing working Windows installers. The only thing that's not
covered is the install and use of Vagrant itself, because the former is
platform-dependent and the latter is basically only the very first terminal
line of http://docs.vagrantup.com/v2/getting-started/ (but read on for a
bit, it's useful).

Feedback on how to document that repo better are very welcome. I'll be
looking at improving the documentation of how to release and what a release
manager does as well soon.

Cheers,
Ralf
Ralf Gommers
10 years ago
Permalink
...
One other thing: would be good to agree how we deal with updates to that
repo. The users of numpy-vendor can be counted on one hand at the moment,
so we probably should be less formal about it then for our other repos. How
about everyone can push simple doc and maintenance updates directly, and
more interesting changes go through a PR that the author can merge himself
after a couple of days? That at least ensures that everyone who follows the
repo gets notified on nontrivial changes.

Ralf
...
Loading...