Changeset 33224 in project


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

Releasing your egg: Remove Google Code, which is in archive mode now and accepts no new repositories.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/releasing-your-egg

    r33223 r33224  
    391391(repo git "http://cgit.example.com/cgit.cgi/{egg-name}")
    392392(uri targz "http://cgit.example.com/{egg-name}/snapshot/{egg-name}-{egg-release}.tar.gz")
    393 (release "0.1")
    394 </enscript>
    395 
    396 ==== Google Code (mercurial, subversion)
    397 
    398 The location of files in Google code is mostly similar for subversion
    399 and mercurial, so we're discussing them in one go.
    400 
    401 ===== Location of release-info file
    402 
    403 On the "source" tab, click "browse" and visit the release-info file.
    404 Ensure that you didn't click any revision numbers, otherwise it will
    405 remember the specific revision you clicked, ''even if that was the
    406 latest''.  Look for the link that says "raw" and copy it.  It should
    407 look something like [[http://my-egg.googlecode.com/hg/my-egg.release-info]]
    408 for Mercurial or [[http://my-egg.googlecode.com/svn/trunk/my-egg.release-info]]
    409 for Subversion.
    410 
    411 ===== Making releases
    412 
    413 Google Code currently does not have a way to automatically serve up
    414 tagged revisions as tarballs.  They have also
    415 [[http://google-opensource.blogspot.com/2013/05/a-change-to-google-code-download-service.html|shut down]]
    416 the ability to host custom downloads, so right now the only way to
    417 host eggs on Google Code is by listing all the files in your egg
    418 in its meta-file.  See [[#meta-file-distribution|the meta-file section]]
    419 at the start of this wiki page to figure out how to set up a {{files}}
    420 section in your meta-file.
    421 
    422 When you have the list set up in your meta-file, you can then point to
    423 it from your release-info file.
    424 
    425 For Mercurial, you can base your release-info file off the following
    426 snippet:
    427 
    428 <enscript highlight="scheme">
    429 (repo hg "https://my-egg.googlecode.com/hg/")
    430 (uri meta-file "http://my-egg.googlecode.com/hg/{egg-name}.meta?r={egg-release}")
    431 (release "0.1")
    432 </enscript>
    433 
    434 For Subversion, you can use this snippet:
    435 
    436 <enscript highlight="scheme">
    437 (repo svn "http://my-egg.googlecode.com/svn/")
    438 (uri meta-file "http://my-egg.googlecode.com/svn/tags/{egg-release}/{egg-name}.meta")
    439393(release "0.1")
    440394</enscript>
Note: See TracChangeset for help on using the changeset viewer.