Hi, there seems to be errors regarding datagard head and the way static
dirs for midcom should be set up when installing midcom-pear. This email
tries to document what has to be done to ues midcom-pear and what
changes are needed in datagard/the next setuptool for midgard.
Allready, I do the following pear command in the buildfile of the
testhost:
pear:
$(PREFIX)/bin/pear upgrade PEAR
$(PREFIX)/bin/pear channel-discover pear.midcom-project.org
$(PREFIX)/bin/pear channel-discover pearified.com
$(PREFIX)/bin/pear install midcom/Role_Mgdschema
$(PREFIX)/bin/pear config-set mgdschema_dir
$(PREFIX)/share/midgard/schema
I guess we need to add a datagard command for setting up pear - or at
least configuring it.
The problem I ran into today was related to the midcom-static directory.
Today the link is set to share/midgard/midcom/static but pear will
install all static files in the PEAR "web_dir" directroy. By default,
this directroy actually points to the root of the directroywhere all
pear packages are installed. Not good.
According to Bergie, the correct way to do this is to point the pear
webdir to another shared folder, probably share/midgard/midcom/static (I
think that is one he's thinking about). So this should probably be added
above:
mkdir -p $(PREFIX)/share/midgard/midcom/static
$(PREFIX)/bin/pear config-set web_dir
$(PREFIX)/share/midgard/midcom/static
Also note that the static dir must be created _before_ midcom-pear is
installed I think.
Regards tarjei
--
Tarjei Huse <
tarjei@nu.n...>
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@midg...
For additional commands, e-mail:
dev-help@midg...
opensubscriber is not affiliated with the authors of this message nor responsible for its content.