Changeset 38675 in project


Ignore:
Timestamp:
05/03/20 02:53:26 (7 months ago)
Author:
evhan
Message:

wiki/releasing-your-egg: Add sourcehut to list of VCS hosting how-tos

File:
1 edited

Legend:

Unmodified
Added
Removed
  • wiki/releasing-your-egg

    r34669 r38675  
    246246</enscript>
    247247
    248 ==== Gitlab (git)
     248==== GitLab (git)
    249249
    250250===== Location of release-info file
     
    258258===== Making releases
    259259
    260 Gitlab makes tags available for download as tarballs.  To find the
     260GitLab makes tags available for download as tarballs.  To find the
    261261location, go to the code browser and switch to a tag at the top left.
    262262On the right side there's a drop-down menu that offers a download for
     
    266266name. If you're using gitlab.com's hosted service and tag your eggs
    267267with the version as tag name, you can use the following release-info
    268 file.  Just don't forget to substitute your Gitlab project name!
     268file.  Just don't forget to substitute your GitLab project name!
    269269
    270270<enscript highlight="scheme">
     
    275275
    276276
    277 ==== Github (git)
     277==== GitHub (git)
    278278
    279279===== Location of release-info file
     
    289289===== Making releases
    290290
    291 Github makes tags available for download as tarballs.  To find the
     291GitHub makes tags available for download as tarballs.  To find the
    292292location, click the big "Downloads" button/link in the code browser.
    293293It will pop up a selection dialog where you can choose between tarball
     
    301301name. If you tag your eggs with the version as tag name, you can use
    302302the following release-info file.  Just don't forget to substitute your
    303 Github username!
     303GitHub username!
    304304
    305305<enscript highlight="scheme">
     
    308308(release "0.1")
    309309</enscript>
     310
    310311
    311312==== Gitweb (git)
     
    336337(release "0.1")
    337338</enscript>
     339
     340
     341==== Sourcehut (mercurial, git)
     342
     343===== Location of release-info file
     344
     345For a Git repository, navigate to the "tree" view for the master branch
     346of your project, select your release-info file and copy the "View raw"
     347link from that page. The URL will look something like this, for user
     348"user" and egg "example":
     349
     350 https://git.sr.ht/~user/example/blob/master/release-info
     351
     352For a Mercurial repository, go to your project's "browse" tab, select
     353your release-info file and copy the "View raw" link. The URL should look
     354like this:
     355
     356 https://hg.sr.ht/~user/example/raw/release-info
     357
     358===== Making releases
     359
     360Sourcehut provides download URLs for tags in both Mercurial and Git
     361repositories. So, in either case you can make a new release by simply
     362tagging your egg.
     363
     364If you use version numbers as tag names, you can use the following
     365release-info files, replacing "USERNAME" with your own. Note the leading
     366tilde, which must be included!
     367
     368For Git:
     369
     370<enscript highlight="scheme">
     371(repo git "https://git.sr.ht/~USERNAME/{egg-name}")
     372(uri targz "https://git.sr.ht/~USERNAME/{egg-name}/archive/{egg-release}.tar.gz")
     373(release "0.1")
     374</enscript>
     375
     376For Mercurial:
     377
     378<enscript highlight="scheme">
     379(repo git "https://hg.sr.ht/~USERNAME/{egg-name}")
     380(uri targz "https://hg.sr.ht/~USERNAME/{egg-name}/archive/{egg-release}.tar.gz")
     381(release "0.1")
     382</enscript>
     383
    338384
    339385==== Cgit (git)
Note: See TracChangeset for help on using the changeset viewer.