• Overview
• Downloads (2)
• Source
• Changesets
• Wiki
• Issues (147) »
  • New issues
  • Open issues
  • Closed issues
  • All issues
  • Advanced query
  • Create new issue
• Forks/Queues (27)
• Followers (113)

Getting the current version of Satchmo

Satchmo has moved to using mercurial for code hosting.

You can clone the repository using https:

$ hg clone https://chris1610@bitbucket.org/chris1610/satchmo/

or, if you have setup your public ssh key,

$ hg clone ssh://hg@bitbucket.org/chris1610/satchmo/

Using Mercurial For Satchmo Development

Prior to June 24, 2009 Satchmo was hosted on svn. On this date, we moved to mercurial in order to support a more open, flexible and collaborative development style. For those not familiar with using mercurial, here is a quick idea of how the development cycle could work.

1. Clone the latest version of the repository. In this example, I'm creating a satchmo-gold to hold the master repository.

$ hg clone http://hg.assembla.com/satchmo satchmo-gold

2. Create a separate local repository for the new feature you want to add. You can create as many of these as you need.

$ hg clone satchmo-gold satchmo-new-feature

3. Make changes to the files in satchmo-new-feature. Make sure to commit the changes. When you commit, you're only adding to the new-feature repository.

$ cd satchmo-new-feature/docs/shipping.txt
$ vi shipping.txt
$ hg commit

4. Pull those changes back to the satchmo-gold repository. At this point we're assuming there are no merge conflicts.

$ cd ../satchmo-gold 
$ hg pull ../satchmo-new-feature
$ hg update

5. Check the changes into the master repository (assuming you have these privileges)

$ hg push