This is an automated notification sent by Gna!.
It relates to:
task #735, project Savane
==============================================================================
LATEST MODIFICATIONS of task #735:
==============================================================================
Posted by: Mathieu Roy <yeupou>
Posted on: 2004-12-27 10:41 (Europe/Paris)
_______________________________________________________
Should Start On: mar 12.10.2004 � 02:00 -> mar 12.10.2004 � 00:00
Should be Finished on: sam 25.12.2004 � 01:00 -> sam 25.12.2004 � 00:00
_______________________________________________________
Follow-up Comment:
Yes, you can create a branch, following procedure described in the doc. Please
open an item to track the branch development.
But the purpose of the branch is to allow development without breaking the
trunk. Not to maintain several version, distro-specific. In other words,
/debian will not move elsewhere and everything entering another branch should,
in the end, be included in the trunk.
Apart from that, you need to set SAVANE_CONF everytime you use a SAVANE_CONF
with is not /etc/savannah.
==============================================================================
OVERVIEW of task #735:
==============================================================================
URL:
<http://gna.org/task/?func=detailitem&item_id=735>
Summary: Support for Gentoo webapp-config: multiple
installation of Savane on the same machine with different configuration files
Project: Savane
Submitted by: tchernobog
Submitted on: mar 07.09.2004 � 17:08
Should Start On: mar 12.10.2004 � 00:00
Should be Finished on: sam 25.12.2004 � 00:00
Category: Backend
Priority: 1 - Later
Status: None
Privacy: Public
Assigned to: None
Percent Complete: 20%
Open/Closed: Open
Effort: 0.00
Planned Release:
_______________________________________________________
This item should start after the merging of the CERN branch.
It should be possible to install savane multiple times on different vhosts on
the same machine, and thus have a different configuration file / database for
each one of them.
This will require some changes in the backend (probably in Savane::Conf?) to
have it using an environment variable (SV_LOCAL_INC_PREFIX), like the frontend
already does.
Else, it'll use the default.
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: lun 27.12.2004 � 10:41 By: Mathieu Roy <yeupou>
Yes, you can create a branch, following procedure described in the doc. Please
open an item to track the branch development.
But the purpose of the branch is to allow development without breaking the
trunk. Not to maintain several version, distro-specific. In other words,
/debian will not move elsewhere and everything entering another branch should,
in the end, be included in the trunk.
Apart from that, you need to set SAVANE_CONF everytime you use a SAVANE_CONF
with is not /etc/savannah.
-------------------------------------------------------
Date: mer 22.12.2004 � 22:09 By: Matteo Settenvini <tchernobog>
Okay, I've trashed my ebuild for the fifth time... I'm getting quite annoyed
:p. There's always something in an approach or another that makes me restart
again. I think I'll end up doing everything the configure+Makefile do by
hand.
So, let's get on it again...
Can I open a branch? It will be a completely separate dir from the rest (let's
say "distro/gentoo", so we can move "debian" under "distro" too), thus it is
granted there'll be no risk.
Btw, can you pass --conffile to the commands in the savane cron.d generated
table? Like sv_mailman? Or do you need SAVANE_CONF? (no problem anyway, just
to know)
-------------------------------------------------------
Date: mer 17.11.2004 � 11:55 By: Matteo Settenvini <tchernobog>
Preparing the ebuild skel.
-------------------------------------------------------
Date: mar 09.11.2004 � 19:19 By: Anonymous
I got my hardware fixed last Friday. I've thought of a couple of
possibilities, but webapp support would always be partial.
Anyway, maybe I came up with something that doesn't touch anything on savane
code. I need some time to implement it, though, and it'll still require an
admin to complete the installation. I'll work it out asap.
Sorry for the delay, but it was due to external causes.
-------------------------------------------------------
Date: mar 09.11.2004 � 18:20 By: Mathieu Roy <yeupou>
Any progress on this task?
-------------------------------------------------------
Date: mar 14.09.2004 � 17:11 By: Mathieu Roy <yeupou>
Latest changes in CERN branch related to this:
SV_LOCAL_INC_PREFIX has been replaced by SAVANE_CONF (SV_LOCAL_INC_PREFIX is
still accepted but no longer documented -- this is an old name who had it's
logic two years ago, but it does no longe make sense).
SAVANE_CONF is honored by both the frontend and the backend.
When SAVANE_CONF is not set, default goes to /etc/savannah, both on frontend
and backend.
Distro scripts should just make sure SAVANE_CONF is set, to allow concurrent
installation of Savane systems.
==============================================================================
This item URL is:
<http://gna.org/task/?func=detailitem&item_id=735>
_______________________________________________
Message post� via/par Gna!
http://gna.org/
_______________________________________________
Savane-dev mailing list
[email protected]
https://mail.gna.org/listinfo/savane-dev
