Changeset 27002 in project for wiki/eggs tutorial


Ignore:
Timestamp:
07/05/12 19:57:16 (9 years ago)
Author:
Mario Domenech Goulart
Message:

eggs tutorial (wiki): add "Managing and hosting eggs" section for better document structure. "Managing eggs in the Chicken hosted repository" and "Managing eggs in your own source control system" are now subsections of "Managing and hosting eggs".

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/eggs tutorial

    r27001 r27002  
    189189exit properly.
    190190
    191 == Managing eggs in the Chicken hosted repository
     191== Managing and hosting eggs
     192
     193=== Managing eggs in the Chicken hosted repository
    192194
    193195If you don't already have your own hosted version control system, you can host your eggs inside the Chicken hosted repository, and let us do the hard work.
    194196
    195 === Obtaining an account in the repository
     197==== Obtaining an account in the repository
    196198
    197199We host Chicken Extensions in the following [[http://subversion.apache.org/|Subversion]] repository:
     
    208210
    209211
    210 === Directory structure
     212==== Directory structure
    211213
    212214The directory for your egg will have the following subdirectories:
     
    220222
    221223
    222 === Importing your files
     224==== Importing your files
    223225
    224226You will initially copy your files to the {{trunk}} directory, add them manually and commit your changes.  For example:
     
    229231 $ svn commit -m "Importing mpeg3 extension."
    230232
    231 === Making a new release
     233==== Making a new release
    232234
    233235Once the code in {{trunk}} is reasonably stable and you want to make a new release, copy it to a new directory under {{tags}}.
     
    241243 $ svn commit -m "Releasing version 1.3."
    242244
    243 == Managing eggs in your own source control system
     245=== Managing eggs in your own source control system
    244246
    245247You can also host your eggs in your own source control system - including distributed ones. To do this, you need to be able to host a publicly-readable repository somewhere.
Note: See TracChangeset for help on using the changeset viewer.