[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#683791: calypso packaging, upstream patches



hello,

i'd like to give a short update on the state of calypso packaging:

* keith's upstream repository (git://keithp.com/git/calypso) contains a
  newly released 1.1 version.

* some of the changes in 1.1 make joe's patches obsolete (addition of a
  man page, http1.1 support). i've merged the patches atop my own ones
  (which are rebased versions of what has been published on the calypso
  mailing list before) atop 1.1 and published them on collab-maint in a
  chrysn/from-joe-nahmias branch.

  patch reviews:

  * "fixup calypso init script": top part is good and important.
    depending on the install location chosen by the debian package,
    DAEMON needs adaption. DISABLE_CALPYSO should be ENABLE_CALPYSO imo,
    and should be checked on restart too.

  * "use ForkingMixIn": joe, have you checked what could happen with
    simultaenous put requests?

  * pam support: did not test it yet

  the others look sound to me.

* keith has published an indepenent packaging approach in the upstream
  repository's debian branch, which does not incorporate any system-wide
  startup routines.

* the own patches mentioned above originally included fixes that would
  make calypso respect xdg and use .config / .local directories for
  their respective purposes. it has been left out for the moment, for
  the following reason:

  given this has not been sorted out in joe's package (which includes
  init routines) either: where should the folder= setting point to for a
  global configuration? should the default (ie builtin) configuration be
  able to detect that it is being run as a "super user" (especially when
  not root)?

  my current personal preference is that calypso by default follow xdg
  basedir spec (ie. not even look up /etc/calypso), and have its paths
  for system wide operation explicitly configured in
  /etc/default/calypso: CALYPSO_OPTS="--configfile=/etc/calypso/config",
  and storage.folder, acl.filename and server.certificate be configured
  there; if that's the way to go, i can provide patches.

keith, joe, what are your preferences for further maintainership? keith,
do you plan to make this a debian native package, as indicated by the
version number?

best regards
chrysn

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom

Attachment: signature.asc
Description: Digital signature


Reply to: