Open Davorak opened 10 years ago
Alright, I think I did this successfully for pre-4.0
tags. I didn't see any tags for 4.0 or later when I pulled from your repo.
That is odd. When I go to my repo I see the post 4.0.0 tags there. I will try and pull them down and push them to a local repo to see if I can replicate the issue.
I replicated the same issue. I am not sure why I did not run in to it on my first attempt however.
Adding --tags
to the pull from my repo fixed the issue on my local
machine and pulled the post 4.0.0 tags.
I have added some commits and some tags that are a content perfect match for what is currently released on hackage. You can browse them at my fork of the package: https://github.com/Davorak/Haskell-Pipes-Library
The format of the tags currently are: hackage-pipes-
I am not attached to the convention but since there were non-trival changes from the existing tags I wanted to name them something different.
With a quick search I could not see how to get the tags over via pull request instructions on how to move the tags to the man repo below.
For 1.0 <= version < 4.0.0 there was an existing commit in the repo that was a perfect match for content as what was released on hackage.
Some changes were needed from existing tags: For versions 4.0.0 <= version <= 4.1.0 I had to remove a few files:
.travis.yml benchmarks/Common.hs README.md laws.md -- On most of them
I have to change the version in the cabal file for 4.0.1(4.0.0 -> 4.0.1)
I used to
nix-prefetch-git
from the nixpkgs package: https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/fetchgit/nix-prefetch-gitIt check for a content match.
This script is used to fetch a git revision and provide a unique hash as part of a process to store it in a immutable store.
Instructions
git remote add <name> https://github.com/Davorak/Haskell-Pipes-Library
git pull <name>
git push --tags