The package manager mostly calls out to git to do stuff in the "correct"
order, but there is very little that Pkg does that you cannot do manually
with git, given that you know what should be done.
// T
On Sunday, September 28, 2014 8:34:31 PM UTC+2, Sal Mangano wrote:
>
> Okay, thanks. I just
Okay, thanks. I just thought there were also things you needed to do with the
Julia Pkg manager as well as at the git level.
I
On Sep 28, 2014, at 2:28 PM, Andreas Noack wrote:
> Then I'm not sure exactly what you are asking about. Each package is a git
> repository so you can just make your ow
Once you've committed your changes, you can say `Pkg.submit("PkgName")`. Looks
like that's still undocumented.
--Tim
On Sunday, September 28, 2014 11:15:23 AM Sal Mangano wrote:
> That is fine. I know how to use git. I guess what I am asking is how to go
> about using the modified and testing th
Then I'm not sure exactly what you are asking about. Each package is a git
repository so you can just make your own branch of it in
~/.julia/SomePackage and when you think it is ready for submission you can
follow the steps from my last mail, i.e. fork, push and open pull request.
Med venlig hilse
That is fine. I know how to use git. I guess what I am asking is how to go
about using the modified and testing the package I modified before I am
ready to commit changes.
Is it something like:
1) Pkg.checkout("SomePackage")
2) Edit the code in ~/.julia/SomePackage/src
3) Pkg.test("SomePackage"
You'll have to know how to use git. It will require some investment costs
if you don't already know how to use it, but it is really convenient for
cooperative package development.
It is a good idea to commit the changes you have made to the package to a
new branch. Then you'll have to fork the ori
Say I install a new Package using Julia's package manager. After using it
for a while I find a bug that I'd like to try to fix myself. Or maybe I'd
like to enhance the package in some way.
What is the recommended workflow for doing this? Do I use
Pkg.checkout('SomePkg') and then edit the source/
El lunes, 7 de abril de 2014 20:09:47 UTC-5, Jameson escribió:
>
> `using X` will always prefer an existing module Main.X over reading
> code off of the hard drive.
>
> or you can prefix it with `include("../DataStructures.jl")`
>
> you may also consider putting your testsuite in a module also
`using X` will always prefer an existing module Main.X over reading
code off of the hard drive.
or you can prefix it with `include("../DataStructures.jl")`
you may also consider putting your testsuite in a module also (and/or
using evalfile instead of include), so that you get an entirely
private
Hi,
I am making some modifications to the DataStructures package to add the
functionality to be able to add new sets in DisjointSets.
>From the command line, it seems to be possible to use
julia> reload("DataStructures.jl")
to load my variant of the code.
My question is about the tests in tes
10 matches
Mail list logo
