|
Hi, boeing 747
Maybe this information will help you
The Spree source code is currently maintained in a Git repository. Git is a distributed version control system (DVCS) and it allows us to do things never before possible with SVN. If you’re skeptical of Git just remember how skeptical you were of SVN when you were using CVS. The differences are subtle but important and they are best understood by hands on use.
The authoritative git repository is hosted by GitHub and is located here. You can clone the git repository using the following command:
git clone git://github.com/railsdog/spree.git spree
If you are planning on contributing to Spree you should create a fork through Git Hub and push fixes to clearly labelled branches (see the Contributors Guide for details.)
If the official GitHub repo is down you can try our mirror at repo.or.cz
1.1 Browsing the Repository and/or Downloading the Source Code
You can easily browse the repository through Git Hub’s excellent visual interface. Git Hub also contains a link to download a tarball copy of the latest source code as well as links to previous versions.
1.2 Git on Windows
There are some well developed Git clients for Windows now. If you are on a Windows box you might want to check out the msygit project. There is also a screencast available.
1.3 SVN
There are no immediate plans to support SVN clients. Given that most of the Rails world is moving to git (including the RoR project itself) maybe this is the time for you to jump on the bandwagon.
1.4 Monitoring Changes in the Source
If you would like to keep up to date on changes to the source you can subscribe to the github RSS feed and you will be notified of all the commits.
2 Building the Gem from the Source
2.1 Motivation
Why bother building the Spree gem from the source? The primary answer is that it allows you to take advantage of all of those great “edge” features without having to wait for the next official release of Spree, and to have this same version of Spree running in all of your projects.
In order to create a new Spree application you will need to run spree which is invoked using the currently installed Spree gem. The spree command is also responsible for setting up your applications’ environment settings, etc. so if you’re trying to build a new store with the cutting edge features, you’ll want to build the gem locally.
Another possibility is “vendor” mode, where a copy of Spree is stored inside your app at location vendor/spree. You can install specific versions or revisions of Spree here: many people use the git submodule feature to track a precise version of Spree inside their projects. The disadvantage is that two projects may not be running the exact same version, i.e. you have to check manually.
2.2 Prerequisites
1. Rails 2.3.x
2. Ruby Gems 1.3.6 or greater
3. Spree gem dependencies (run rake gems to check, rake gems:install to install)
4. The Jeweler gem (which pulls in a Git gem and Gemcutter too – use (sudo) gem install jeweler)
Gem building no longer runs all of the tests.
It is suggested that you get Spree up and running using the source first before attempting to build the gem. This will be the easiest way to make sure you have all of the correct dependencies, etc.
2.3 Performing the Actual Build
First, you should create/update the gemspec. You must have the Jeweler gem installed for this.
Use the following command to build the gem
rake build
Now you can install the gem, replacing X,Y,Z with the appropriate numbers
sudo gem install pkg/spree-X.Y.Z.gem
The exact version of the gem will correspond to whatever version reflects the state of the edge code at the time you build it._
2.4 Considerations
* An edge gem will have a x.y.99 version number. This denotes an “edge” version. You may need to uninstall the edge gem later if you want to work with the x.y.z gem once it is released.
* If you want to deploy the gem on multiple machines: the built gem is in the spree source directory, in pkg/. Just copy it and install it, eg sudo gem install spree-0.8.99.gem
* You may want to do rm -rf pkg to clean things up from previous build attempts before building the gem again.
Good luck
__________________
websitetemplates[dot]bz
|
Before you post, read our: 
