developer.jelix.org is not used any more and exists only for history. Post new tickets on the Github account.
developer.jelix.org n'est plus utilisée, et existe uniquement pour son historique. Postez les nouveaux tickets sur le compte github.

Changes between Version 6 and Version 7 of en/sources


Ignore:
Timestamp:
Aug 20, 2011, 10:09:02 AM (9 years ago)
Author:
laurentj
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • en/sources

    v6 v7  
    66== Principles ==
    77
    8 Sources stored in the Mercurial repository are not ready to be performed by PHP. There are some preprocessing instructions in some php files, so, sources should be parsed by a preprocessor in order to be used by PHP. This preprocessing instruction allow to build packages for some specific PHP configurations, or some specific jelix editions.
     8Sources stored in the GIT repository are not ready to be performed by PHP. There are some preprocessing instructions in some php files, so, sources should be parsed by a preprocessor in order to be used by PHP. This preprocessing instruction allow to build packages for some specific PHP configurations, or some specific jelix editions.
    99
    1010So, here is the process :
    1111
    12  1. get sources of jelix from the Mercurial repository (hg clone)
     12 1. get sources of jelix from [https://github.com/jelix/jelix the git repository] (git clone)
    1313 1. create an ini file which contains options for the builder
    1414 1. launch the build/buildjelix.php script by giving the ini file, then you have in an other directory the php files of jelix
     
    1717For a contributeur of course he will do :
    1818
    19  1. gets sources of jelix from the Mercurial repository (hg clone)
     19 1. gets sources of jelix from the repository
    2020 1. makes modification in sources (bug fix, new feature..)
    2121 1. creates an ini file which contains options for the builder
     
    2727== Getting sources ==
    2828
    29 We use [http://mercurial.selenic.com/ Mercurial] to store sources of jelix and to follow the history of modifications. So you have to install a mercurial client on your machine. Then you can access to the repository by giving the address of the repository to mercurial commands.
     29We use [http://git-scm.com/ Git] to store sources of jelix and to follow the history of modifications. So you have to install a Git client on your machine. Then you can access to the repository by giving the address of the repository to git commands. See instructions on Github.com.
    3030
     31In the past, we used subversion (January 2006 - June 2009), then Mercurial on our own server (June 2009 - March 2010), and [http://bitbucket.org/jelix/ on Bitbucket] (March 2010 - August 2011).
    3132The official repositories of Jelix are on Bitbucket (since March 2010).
    32 
    33 For "anonymous" contributors, the address is:
    34 
    35 {{{
    36    http://bitbucket.org/jelix/jelix-trunk
    37 }}}
    38 
    39 
    40 For contributors who have the right to commit into the repository :
    41 
    42 {{{
    43    ssh://hg@bitbucket.org/jelix/jelix-trunk
    44 }}}
    45 
    46 
    47 
    48 
    49 
    50 So, in a command line, you type
    51 {{{
    52 hg clone http://bitbucket.org/jelix/jelix-trunk
    53 }}}
    54 or
    55 {{{
    56 hg clone ssh://hg@bitbucket.org/jelix/jelix-trunk
    57 }}}
    58 
    59 Of course, If you are registered on bitbucket.org, you can "fork" the repository directly into your bitbucket account, so it is a way to publish your changes.
    6033
    6134
    6235== Directories ==
    6336
    64 The 'jelix-trunk' directory contains latest improvements for the next major release, and the 'branches' directory contains a directory for each minor releases. In these directories, we only fix bugs. No major new features are commited in them.
     37The master branch contains latest improvements for the next major release, and branches named jelix-x.y are branches of stable releases. In these branches, we only fix bugs. No major new features are commited in them.
    6538
    66 
    67 The directories you find in this directories are:
     39The directories you find are:
    6840
    6941 * build: the scripts to build jelix sources
     
    8153Before doing modifications, you should prepare an working environment: a directory where the built files of jelix will be stored. In this "target" directory, you could use jelix in your applications. Example:
    8254
    83 Your local copy of the subversion repository could be at:
     55Your local copy of the repository could be at:
    8456{{{
    85    /home/laurent/projects/jelix/hg/
     57   /home/laurent/projects/jelix/src/
    8658}}}
    8759