Changeset 33222 in project


Ignore:
Timestamp:
02/27/16 19:54:23 (3 years ago)
Author:
sjamaan
Message:

Releasing your egg: add cgit to the list

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/releasing-your-egg

    r32495 r33222  
    329329something like this, for an egg "foo":
    330330
    331 {{{http://gitweb/gitweb.cgi?p=foo.git;a=blob_plain;f=foo.release-info}}}
     331 http://gitweb/gitweb.cgi?p=foo.git;a=blob_plain;f=foo.release-info
    332332
    333333===== Making releases
     
    336336through Gitweb with a query string like the following:
    337337
    338 {{{http://gitweb/gitweb.cgi?p={egg-name}.git;a=snapshot;h=refs/tags/{egg-release};sf=tgz}}}
     338 http://gitweb/gitweb.cgi?p={egg-name}.git;a=snapshot;h=refs/tags/{egg-release};sf=tgz
    339339
    340340So, if you tag each release and use a release-info file like the
     
    346346(repo git "git://gitweb/{egg-name}.git")
    347347(uri targz "http://gitweb/gitweb.cgi?p={egg-name}.git;a=snapshot;h=refs/tags/{egg-release};sf=tgz")
     348(release "0.1")
     349</enscript>
     350
     351==== Cgit (git)
     352
     353===== Location of release-info file
     354
     355Navigate to the "tree" view for the master branch of your project and
     356copy the "plain" link for your release-info file (it's all the way to
     357the right). The link will look something like this, for an egg "foo":
     358
     359 http://cgit.example.com/foo/plain/foo.release-info
     360
     361For example, the release info for the [[/eggref/4/hardwood|Hardwood
     362egg]] looks like this:
     363
     364[[http://www.upyum.com/cgit.cgi/hardwood/plain/hardwood.release-info]]
     365
     366The {{cgit.cgi}} part is optional, depending on how cgit was
     367configured.  For example, the release-info for the
     368[[/eggref/4/scsh-process|scsh-process egg]] looks like this:
     369
     370[[http://code.more-magic.net/scsh-process/plain/scsh-process.release-info]]
     371
     372===== Making releases
     373
     374The download link for a tarball of a specific Git tag can be found by
     375visiting "refs", then the tag, following it to the commit and if
     376snapshots are shown there should be a download link, but it links
     377directly to the commit hash.  You can simply replace the hash with the
     378symbolic tag name.
     379
     380If snapshots are not shown, it's still possible to construct the link
     381manually, and it will work:
     382
     383 http://cgit.example.com/cgit.cgi/{egg-name}/snapshot/{egg-name}-{egg-release}.tar.gz
     384
     385So, if you tag each release and use a release-info file like the
     386following, every new tag will be made available as a tarball at that
     387URL (make sure to substitute your Git URL and Cgit host into
     388{{{repo}}} and {{{uri}}} strings):
     389
     390<enscript highlight="scheme">
     391(repo git "http://cgit.example.com/cgit.cgi/{egg-name}")
     392(uri targz "http://cgit.example.com/{egg-name}/snapshot/{egg-name}-{egg-release}.tar.gz")
    348393(release "0.1")
    349394</enscript>
Note: See TracChangeset for help on using the changeset viewer.