I have two projects that I intend to put on hackage soon. One depends on the other. I have "cabaled" both. I am wondering how others work with this kind of set up where changes are made to both libraries as they work. -- Tony Morris http://tmorris.net/
Tony Morris wrote:
I have two projects that I intend to put on hackage soon. One depends on the other. I have "cabaled" both. I am wondering how others work with this kind of set up where changes are made to both libraries as they work.
You just update and re-upload the packages as necessary. It really helps here if you follow the versioning guidelines: http://www.haskell.org/haskellwiki/Package_versioning_policy HTH, Martijn.
I don't want to have to upload every time I make a minor change as I am working. Surely there is an easier way. Martijn van Steenbergen wrote:
Tony Morris wrote:
I have two projects that I intend to put on hackage soon. One depends on the other. I have "cabaled" both. I am wondering how others work with this kind of set up where changes are made to both libraries as they work.
You just update and re-upload the packages as necessary. It really helps here if you follow the versioning guidelines:
http://www.haskell.org/haskellwiki/Package_versioning_policy
HTH,
Martijn.
-- Tony Morris http://tmorris.net/
To install a package from local sources, just run 'cabal install' in the directory with the package's .cabal file. Tony Morris wrote:
I don't want to have to upload every time I make a minor change as I am working. Surely there is an easier way.
Martijn van Steenbergen wrote:
Tony Morris wrote:
I have two projects that I intend to put on hackage soon. One depends on the other. I have "cabaled" both. I am wondering how others work with this kind of set up where changes are made to both libraries as they work.
You just update and re-upload the packages as necessary. It really helps here if you follow the versioning guidelines:
http://www.haskell.org/haskellwiki/Package_versioning_policy
HTH,
Martijn.
=============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ===============================================================================
On Wed, Nov 11, 2009 at 10:26:32AM -0000, Sittampalam, Ganesh wrote:
To install a package from local sources, just run 'cabal install' in the directory with the package's .cabal file.
You can even have some kind of script like cd lib1 cabal install || exit 1 cd ../lib2 cabal install || exit 2 -- Felipe.
On Wednesday 11 November 2009 08:23:53 am Tony Morris wrote:
I have two projects that I intend to put on hackage soon. One depends on the other. I have "cabaled" both. I am wondering how others work with this kind of set up where changes are made to both libraries as they work.
What i did in situations like this, is the following: If B depends on A: 1. Uninstall A (for not mistakenly link to an old version.) 2. Add the source directories of a local copy of A to the src-dirs in the cabal file of B. 3. remove the dependency of A in the cabal file of B. I know, that this is not very elegant, though. You end up changing your cabal file very often :( If you could tell cabal, which cabal file to use, the situation would be a little better, i think. Sönke
participants (5)
-
Felipe Lessa -
Martijn van Steenbergen -
Sittampalam, Ganesh -
Sönke Hahn -
Tony Morris