Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 27 Nov 2010 02:07:50 +0000 (UTC)
From:      "Philip M. Gollucci" <pgollucci@FreeBSD.org>
To:        ports-committers@FreeBSD.org, cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org
Subject:   cvs commit: ports/devel Makefile ports/devel/py-mercurialserver Makefile distinfo pkg-descr pkg-install pkg-plist ports/devel/py-mercurialserver/files patch-setup.py
Message-ID:  <201011270207.oAR27oJw044083@repoman.freebsd.org>

next in thread | raw e-mail | index | archive | help
pgollucci    2010-11-27 02:07:50 UTC

  FreeBSD ports repository

  Modified files:
    devel                Makefile 
  Added files:
    devel/py-mercurialserver Makefile distinfo pkg-descr 
                             pkg-install pkg-plist 
    devel/py-mercurialserver/files patch-setup.py 
  Log:
  mercurial-server gives your developers remote read/write access to centralized
  Mercurial repositories using SSH public key authentication; it provides
  convenient and fine-grained key management and access control.
  
  All of the repositories controlled by mercurial-server are owned by a single
  user (the "hg" user in what follows), but many remote users can act on them,
  and different users can have different permissions. We don't use file
  permissions to achieve that - instead, developers log in as the "hg" user
  when they connect to the repository host using SSH, using SSH URLs of the
  form "ssh://hg@repository-host/repository-name". A restricted shell prevents
  them from using this access for unauthorized purposes. Developers
  are authenticated only using SSH keys; no other form of authentication is
  supported.
  
  To give a user access to the repository, place their key in an
  appropriately-named subdirectory of "/usr/lcoal/etc/mercurialserver/keys"
  and run "refresh-auth". You can then control what access they have to what
  repositories by editing the control file
  "/usr/local/etc/mercurialserver/access.conf", which can match the names of
  these keys against a glob pattern.
  
  For convenient remote control of access, you can instead (if you have the
  privileges) make changes to a special repository called "hgadmin", which
  contains its own "access.conf" file and "keys" directory. Changes pushed to
  this repository take effect immediately. The two "access.conf" files are
  concatenated, and the keys directories merged.
  
  WWW: http://www.lshift.net/mercurial-server.html
  
  PR:             ports/151993
  Submitted by:   Aldis Berjoza <aldis at bsdroot.lv>
  
  Revision  Changes    Path
  1.4146    +1 -0      ports/devel/Makefile
  1.1       +62 -0     ports/devel/py-mercurialserver/Makefile (new)
  1.1       +2 -0      ports/devel/py-mercurialserver/distinfo (new)
  1.1       +11 -0     ports/devel/py-mercurialserver/files/patch-setup.py (new)
  1.1       +28 -0     ports/devel/py-mercurialserver/pkg-descr (new)
  1.1       +43 -0     ports/devel/py-mercurialserver/pkg-install (new)
  1.1       +39 -0     ports/devel/py-mercurialserver/pkg-plist (new)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201011270207.oAR27oJw044083>