This is a multipart message in MIME format.
--=_alternative 0053AC09C1257057_=
Content-Type: text/plain; charset="us-ascii"

Send me the lines you need looked at, or send them to the list and we can
distribute the task.

doug






Ondra Koutek
08/08/05 01:50 PM
Please respond to campsite-dev


To: campsite-dev@campware.org
cc:
Subject: [campsite-dev] Campsite FreeBSD port progress


Hi all,
I am working on FreeBSD port of campsite 2.3, so if you know about
someone having some work done, let him contact me.

I have some work done. Now I would like some help from Doug:
There is a file describing the campsite in about 10-20 lines plain text.
There is a single line port description.
I would welcomme some oficial english texts to put there

Next I would like to know, what is BUILD dependency (What must be
installed to have make done correctly) and what id RUN dependency (what
do I need for campsite to run)

Ondra




--=_alternative 0053AC09C1257057_=
Content-Type: text/html; charset="us-ascii"



Send me the lines you need looked at, or send them to the list and we can distribute the task.



doug

Ondra Koutek <kouteko@tol.org> 08/08/05 01:50 PM Please respond to campsite-dev

To:        campsite-dev@campware.org         cc:                 Subject:        [campsite-dev] Campsite FreeBSD port progress

Hi all,

I am working on FreeBSD port of campsite 2.3, so if you know about

someone having some work done, let him contact me.



I have some work done. Now I would like some help from Doug:

There is a file describing the campsite in about 10-20 lines plain text.

There is a single line port description.

I would welcomme some oficial english texts to put there



Next I would like to know, what is BUILD dependency (What must be

installed to have make done correctly) and what id RUN dependency (what

do I need for campsite to run)



Ondra








--=_alternative 0053AC09C1257057_=--

------------------------------------------
Posted to Phorum via PhorumMail

This is a multipart message in MIME format.
--=_alternative 00577BEAC1257057_=
Content-Type: text/plain; charset="us-ascii"

In general, the text is pretty good. My changes are below. Anybody else
want to jump in?- doug

Comment:
A free and open multilingual web publishing tool for news sites

Description file:
Campsite is a multilingual content management system (CMS) for news
websites.

Campsite follows a print publication paradigm, so it structures sites by
default as Publications> Issues > Sections > Articles. Campsite works best
for medium-to-large-size online news publications, but it is capable of
handling smaller sites as well. Some of its main features are ease of use,
total design freedom for web designers, built-in subscription support,
automatic publishing, easy article translation and internationalization.








Ondra Koutek
08/08/05 05:22 PM
Please respond to campsite-dev


To: campsite-dev@campware.org
cc:
Subject: Re: [campsite-dev] Campsite FreeBSD port progress


I used some from campware site:

Comment:
The free and open multilingual web publishing tool for news sites

Description file:
Campsite is a multilingual content management system (CMS) for news
websites.

Campsite follows the print-newspaper publishing paradigm, so it structures
sites
by default as Publications> Issues > Sections > Articles.
Campsite works best for medium-to-large-size online news publications,
but it is capable of handling nimbler sites too.
Some of its main features are highly customizable user interface,
total design freedom for web designers, automatic creation of archives,
copy flow, and built-in subscription support.

WWW: http://www.campware.org/






--=_alternative 00577BEAC1257057_=
Content-Type: text/html; charset="us-ascii"



In general, the text is pretty good. My changes are below. Anybody else want to jump in?- doug



Comment:

A free and open multilingual web publishing tool for news sites



Description file:

Campsite is a multilingual content management system (CMS) for news websites.



Campsite follows a print publication paradigm, so it structures sites by default as Publications> Issues > Sections > Articles. Campsite works best for medium-to-large-size online news publications, but it is capable of handling smaller sites as well. Some of its main features are ease of use, total design freedom for web designers, built-in subscription support, automatic publishing, easy article translation and internationalization.

Ondra Koutek <kouteko@tol.org> 08/08/05 05:22 PM Please respond to campsite-dev

To:        campsite-dev@campware.org         cc:                 Subject:        Re: [campsite-dev] Campsite FreeBSD port progress

I used some from campware site:



Comment:

The free and open multilingual web publishing tool for news sites



Description file:

Campsite is a multilingual content management system (CMS) for news websites.



Campsite follows the print-newspaper publishing paradigm, so it structures sites

by default as Publications> Issues > Sections > Articles.

Campsite works best for medium-to-large-size online news publications,

but it is capable of handling nimbler sites too.

Some of its main features are highly customizable user interface,

total design freedom for web designers, automatic creation of archives,

copy flow, and built-in subscription support.



WWW: http://www.campware.org/












--=_alternative 00577BEAC1257057_=--

------------------------------------------
Posted to Phorum via PhorumMail

> Next I would like to know, what is BUILD dependency (What must be
> installed to have make done correctly) and what id RUN dependency (what
> do I need for campsite to run)
Most of the applications/libraries you need Campsite to run are listed in
INSTALL file. I would add:
- libxml 2.6.x or greater
- libstdc++ (STL - Standard Templates Library for C++)
- standard command line tools: pwd, ls, mkdir, chown, chmod, cat, cut, grep,
cp, rm, locate, passwd, group, killall, convert
- PEAR

All of these are detected by the install script so you can't install campsite
without these dependencies.

Mugur




____________________________________________________
Start your day with Yahoo! - make it your home page
http://www.yahoo.com/r/hs

------------------------------------------
Posted to Phorum via PhorumMail

Here are the runtime dependencies I came up with for Campsite when I
build the RPM. I patched it so that perl Text::Aspell was not required.
ADODB is not required since it is bundled with. Ditto Smarty.

[john@jdpipe ~]$ rpm -q --requires campsite
/bin/bash
/bin/sh
/bin/sh
/bin/sh
/usr/bin/perl
config(campsite) = 2.3.0-2
libc.so.6
libc.so.6(GLIBC_2.0)
libc.so.6(GLIBC_2.1)
libc.so.6(GLIBC_2.1.2)
libc.so.6(GLIBC_2.1.3)
libcom_err.so.2
libcrypt.so.1
libcrypto.so.4
libcurl.so.3
libdl.so.2
libgcc_s.so.1
libgcc_s.so.1(GCC_3.0)
libgssapi_krb5.so.2
libidn.so.11
libk5crypto.so.3
libkrb5.so.3
libm.so.6
libmysqlclient.so.10
libnsl.so.1
libpthread.so.0
libpthread.so.0(GLIBC_2.0)
libpthread.so.0(GLIBC_2.1)
libpthread.so.0(GLIBC_2.3.2)
libresolv.so.2
libssl.so.4
libstdc++.so.6
libstdc++.so.6(CXXABI_1.3)
libstdc++.so.6(GLIBCXX_3.4)
libxml2.so.2
libz.so.1
mysql >= 3.23.58
perl >= 5.8.5
perl(CGI)
perl(Encode)
perl(Time::HiRes)
perl(XML::DOM)
perl(strict)
perl(utf8)
php >= 4.3
php-pear >= 4.3.11
rpmlib(CompressedFileNames) <= 3.0.4-1
rpmlib(PayloadFilesHavePrefix) <= 4.0-1
scrollkeeper >= 0.3.14
vixie-cron >= 4.1


Mugur Rus wrote:

>>Next I would like to know, what is BUILD dependency (What must be
>>installed to have make done correctly) and what id RUN dependency (what
>>do I need for campsite to run)
>>
>>
>Most of the applications/libraries you need Campsite to run are listed in
>INSTALL file. I would add:
>- libxml 2.6.x or greater
>- libstdc++ (STL - Standard Templates Library for C++)
>- standard command line tools: pwd, ls, mkdir, chown, chmod, cat, cut, grep,
>cp, rm, locate, passwd, group, killall, convert
>- PEAR
>
>All of these are detected by the install script so you can't install campsite
>without these dependencies.
>
>Mugur
>
>
>
>
>____________________________________________________
>Start your day with Yahoo! - make it your home page
>http://www.yahoo.com/r/hs
>
>
>
>

------------------------------------------
Posted to Phorum via PhorumMail

My idea is to provide port with extra patches specially for FreeBSD so
that Mugur and others do not have to change sources due to FreeBSD
anymore.
Also there is a big push in FreeBSD to keep server's consistency and
reduce number of dependencies as much possible.
example:
I do not have Apache version as an dependency, just proclaim to need
apache. The same is with MySQL. I run campsite myself on 4.1 and do not
want port to depend on any particular version of MySQL.

Ondra


On Thu, 2005-08-11 at 13:47 +1000, John Pye wrote:
> Note that MySQL version 4.0 is supposed to be required as well, but I've
> managed to run everything except the upgrade scripts using mysql 3.23.
> So my RPM only requires 3.23 for now, since 4.0 is not installed by
> default on FC3.
> JP
>
> Mugur Rus wrote:
>
> >>Most of the applications/libraries you need Campsite to run are listed in
> >>INSTALL file. I would add:
> >>- libxml 2.6.x or greater
> >>- libstdc++ (STL - Standard Templates Library for C++)
> >>- standard command line tools: pwd, ls, mkdir, chown, chmod, cat, cut, grep,
> >>cp, rm, locate, passwd, group, killall, convert
> >>- PEAR
> >>
> >>
> >Add iconv to command line tools.
> >
> >Mugur
> >
> >
> >
> >
> >____________________________________________________
> >Start your day with Yahoo! - make it your home page
> >http://www.yahoo.com/r/hs
> >
> >
> >
> >
>

------------------------------------------
Posted to Phorum via PhorumMail

This might be quite difficult, because FreeBSD is not Linux though there
are more differences you would expect and as developers work on Linux,
most of these differences are discovered on fly.
Also FreeBSD idea of packaging is different from the one known from
Linux. People say, that Linux is just kernel and bunch of packages,
while FreeBSD is whole OS plus some additional packages, that needs to
respect FreeBSD OS rules.
So if you want make campsite usable on FreeBSD, than we can work
together. However if we would like to make campsite to be native FreeBSD
application, we can do that, but we have to split.

About packaging systems, FreeBSD has source based packages, that can be
build into binary package and distributed in both forms.
Difference is, that while on Linux you create package for some
distribution and simply expects everything to be exact depending on the
distribution, FreeBSD packages expect admin to handle his server in any
matter he wish and packages respects it.
As an example I can notice /bin/bash location.
In Linux it is set to be in /bin.
In FreeBSD the default path is /usr/local/bin, so the patch for FreeBSD
should contain all bash parts and replace it by /usr/local/bin/bash.
However in FreeBSD admin can decide, he likes his bash
in /usr/local/sbin for some reason (usually some application that has
location hard coded). Therefore there is a push to respect the
abnormalities and this change is not done by patch, but at the time of
installing/compiling you check the location of bash and use find and
replace (part of FreeBSD ports system) to make new application to use
correct location of bash.
Second example of difference is the start script. Now the install places
start to rc.local, which is not anymore FreeBSD start script and though
it will not be executed. But there is still a chance, that some admin
uses it. So I had to find the place, where this script is created and
used patch to coment out the code not to generate rc.local.
Than I used campsite start script from /usr/local/campsite/bin and made
a copy to the port files. When port is installed, I use this copy to
move to proper folder. And the reason? FreeBSD uses its own form of rc
scripts, so in the future I need to change this start script to be more
FreeBSD like, so that FreeBSD admin can handle the script the same way
as other FreeBSD port apps.

Of course at the moment something deeper inside campsite is wrong, I
prefer to discuss it here or in mantis/trac

One more thing for the future. After CS is moved to PHP, do we still
need some install? In my opinion it would be much better to get rid of
its need and simply make campsite ports and packages only to move files
to proper place and than to write some config utility, which should be
written anyways. (Meaning a tool in PHP or in shell, that will enable
admin to maintain instances and make some configurations)

Ondra

On Thu, 2005-08-11 at 18:01 +1000, John Pye wrote:
> Hi Ondra
>
> I think it's important to feed back the patches that result from
> platform-specific builds, becuase that way you move your code towards
> being platform-independent, and it reduces the packaging process for
> later versions of the software. Obviously it takes a bit of work though.
> Maybe we can work together on this to try to minimise the patch that
> will work for both of us?
>
> Here are the patches I used for my current RPM version. They will open
> and view nicely with the KDE program "kompare", or you can just apply
> them if you want like this:
>
> bzip2 -d campsite-2.3.0.patch
> tar zxf campsite-2.3.0.tar.gz
> cd campsite
> patch -p1 < ../campsite-2.3.0.patch
>
> Am I right in thinking that the packaging process for FreeBSD is a
> source-code build? In other words your final package does not contain
> compiled code, but rather contains some kind of script that compiles and
> installs the code in a standard environment, with some dependency checking?
>
> I've attached my RPM 'spec' file as well, just in case it's of any use
> to you.
>
> I'd be keen to hear about your decisions for suitable directories for
> campsite on the FreeBSD system. The default install uses /usr/local but
> if you're packaging software you shouldn't be using the /usr/local
> directory eh. I've gone for
>
> /usr/share/campsite for instance templates and backup files
> /usr/bin for all executables
> /etc/campsite for settings
> /usr/share/campsite/www-common for common WWW files
> /var/www/campsite/xxxx for instances (default instance would then be
> /var/www/campsite/campsite/html/look... etc; I thought about using
> /var/www/publications/... but that's less clear?)
> /usr/share/doc/... for the manual (FC3 standard location)
>
> On FC3 there is a standard directory where you can drop Apache conf
> files - /etc/httpd/conf.d/ - which in theory allows you to install
> web-based software without requiring that the person manually edit their
> httpd.conf. Do you have anything like that on a standard BSD build?
>
> JP
>
> Ondra Koutek wrote:
>
> >My idea is to provide port with extra patches specially for FreeBSD so
> >that Mugur and others do not have to change sources due to FreeBSD
> >anymore.
> >Also there is a big push in FreeBSD to keep server's consistency and
> >reduce number of dependencies as much possible.
> >example:
> >I do not have Apache version as an dependency, just proclaim to need
> >apache. The same is with MySQL. I run campsite myself on 4.1 and do not
> >want port to depend on any particular version of MySQL.
> >
> >Ondra
> >
> >
> >On Thu, 2005-08-11 at 13:47 +1000, John Pye wrote:
> >
> >
> >>Note that MySQL version 4.0 is supposed to be required as well, but I've
> >>managed to run everything except the upgrade scripts using mysql 3.23.
> >>So my RPM only requires 3.23 for now, since 4.0 is not installed by
> >>default on FC3.
> >>JP
> >>
> >>Mugur Rus wrote:
> >>
> >>
> >>
> >>>>Most of the applications/libraries you need Campsite to run are listed in
> >>>>INSTALL file. I would add:
> >>>>- libxml 2.6.x or greater
> >>>>- libstdc++ (STL - Standard Templates Library for C++)
> >>>>- standard command line tools: pwd, ls, mkdir, chown, chmod, cat, cut, grep,
> >>>>cp, rm, locate, passwd, group, killall, convert
> >>>>- PEAR
> >>>>
> >>>>
> >>>>
> >>>>
> >>>Add iconv to command line tools.
> >>>
> >>>Mugur
> >>>
> >>>
> >>>
> >>>
> >>>____________________________________________________
> >>>Start your day with Yahoo! - make it your home page
> >>>http://www.yahoo.com/r/hs
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
> plain text document attachment (campsite.spec)
> %define wwwdir /var/www
> %define campsitewww /var/www/campsite
> %define campsitedir %_datadir/campsite
> %define campsitewwwcommon %campsitedir/www-common
> %define campsiteetc %_sysconfdir/campsite
>
> Summary: A multilingual content management system (CMS) for news websites.
> Name: campsite
> Version: 2.3.0
> Release: 2
> License: GPL
> Group: Applications/Internet
> Source: http://www.campware.org/look/campware/download/%{name}-%{version}.tar.gz
> Patch: http://www.curioussymbols.com/campsite/%{name}-%{version}.patch
>
> URL: http://www.campware.org/
> BuildRoot: %{_tmppath}/%{name}-%{version}-root
> Provides: campsite
>
> Requires: php >= 4.3
> Requires: mysql >= 3.23.58
> Requires: php-pear >= 4.3.11
> Requires: perl >= 5.8.5
> Requires: scrollkeeper >= 0.3.14
> Requires: vixie-cron >= 4.1
>
> %description
> Campsite is a multilingual content management system (CMS) for news websites.
>
> Campsite's easily localizable user interface was built with the end user (journalist/editor/publisher) in mind and it can be configured to suit different profiles of end users – to each according his or her own technological prowess.
>
> Campsite follows the print-newspaper publishing paradigm, so it structures sites by default as Publications> Issues > Sections > Articles. Campsite works best for medium-to-large-size online news publications, but it is capable of handling nimbler sites too. Some of its main features are highly customizable user interface, total design freedom for web designers, automatic creation of archives, copy flow, and built-in subscription support.
>
> RPM NOTE:
>
> After installing your RPM, you must perform the following steps to complete installation:
>
> 1. log in as root and type 'create_instance --db_password XXXX', where XXXX is your MySQL root password
> 2. Copy the file /etc/campsite/campsite/campsite-vhost.conf to /etc/httpd/conf.d/campsite.conf
> 3. Edit the new file, substituting \$SERVER_ADDRESS and \$SERVER_NAME with the values you wish to use.
> 4. Add the the line "php_admin_value include_patch .:/usr/share/pear" to point to where you have PEAR installed
> 5. Restart your webserver, /sbin/service httpd restart
> 6. You may need to run some additional 'pear' commands: "pear install File_Find", etc.
> 7. Nothing will work until you have some templates. You can log into you new campsite and create
> some, or you can unpack the demo templates from www.campware.org
> 8. You will also need to define article types etc in campsite admin.
>
> CHANGES IN VERSION 2.3.0:
>
> - A brand new WYSIWYG text editor was introduced, goodbye HTMLArea, hello Xinha (HTMLArea's more dynamically supported offspring), featuring a MSWord style-tag killer.
>
> - Enhanced user management - separation of staff & subscribers, ability to search users, new, easier-to-use interface, categorized user-rights list
>
> - A new and improved Localizer - new, easier-to-use interface, ability to translate from any language to any other language, ability to change your default language, etc.
>
> - Online help with user comments
>
> - A revamped starting (Home) page, including lists of recently published articles, and pending scheduled publishing actions on the home page
>
> - Many other user-interface enhancements and bug fixes (for a full list of changes, cliick here)
>
>
> #
> # DESIGN ISSUES WITH THIS RPM
> #
> # Getting campsite to build as an RPM was pretty tricky. Campsite has a very complex interactive installation
> # procedure, much more complex that I anticipated. A big problem came from the fact that RPM requires files to
> # be relocatably installed to 'buildroot' although the files will finally (in operation) be residing in a
> # different location. So files like 'campsite_config' need to refer to the INSTALLED file locations but
> # all the Makefiles etc need to refer to the files in the RPM_BUILD_ROOT location.
> #
> # In order to facilitate this, I changed basically all of the 'install' sections of the Makefiles and a few of
> # the shell scripts to use $ROOT in front on the (previously absolution) file installation paths.
> #
> # I also added $ROOT in front of locations like /etc/rd.d/rc.local. Any file that is going to be
> # added/modified by RPM needs to be tracked by RPM, and so needs to be created under the RPM_BUILD_ROOT.
> #
> # Some problems occurred with Perl module dependencies. Files in the HTMLAREA distribution required Perl:Aspell
> # and
> #
> %prep
> rm -rf %{buildroot}
> %setup -q -n campsite
> %patch -p 1
>
>
> %build
> cat > .install_conf/install_conf.php << ____EOF____
> >
> \$Campsite['APACHE_USER'] = 'apache';
> \$Campsite['APACHE_GROUP'] = 'apache';
> \$Campsite['CAMPSITE_DIR'] = '%campsitedir';
> \$Campsite['BIN_DIR'] = '%_bindir';
> \$Campsite['ETC_DIR'] = '%campsiteetc';
> \$Campsite['WWW_DIR'] = '%campsitewww';
> \$Campsite['WWW_COMMON_DIR'] = '%campsitewwwcommon';
> \$Campsite['DEFAULT_SMTP_SERVER_ADDRESS'] = 'localhost';
> \$Campsite['DEFAULT_SMTP_SERVER_PORT'] = '25';
> \$Campsite['DEFAULT_DATABASE_SERVER_ADDRESS'] = 'localhost';
>
> \$CampsiteVars['install'] = array('APACHE_USER', 'APACHE_GROUP', 'CAMPSITE_DIR', 'BIN_DIR', 'ETC_DIR', 'WWW_DIR', 'WWW_COMMON_DIR', 'DEFAULT_SMTP_SERVER_ADDRESS', 'DEFAULT_SMTP_SERVER_PORT', 'DEFAULT_DATABASE_SERVER_ADDRESS');
>
> ?>
> ____EOF____
>
>
> ./configure --campsite_dir %campsitedir --bin_dir %_bindir --etc_dir %campsiteetc --www_dir %campsitewww --www_common_dir %campsitewwwcommon
> make
>
> %install
> mkdir -p %{buildroot}/etc/init.d
> mkdir -p %{buildroot}/etc/cron.d
>
> make -e BUILD_ROOT=%{buildroot} install
>
> ## INSTALL DOCUMENTATION
> mkdir -p -m 755 %{buildroot}%_datadir/omf
> install -m 744 -o root -g root -p documentation/campsite.omf %{buildroot}%_datadir/omf/campsite.omf
>
> %clean
> rm -rf %{buildroot}
>
> %post
> # %{buildroot}/usr/bin/create_instance
> ln -s %_sysconfdir/init.d/campsite %_sysconfdir/rc3.d/S95campsite
> ln -s %_sysconfdir/init.d/campsite %_sysconfdir/rc5.d/S95campsite
> ln -s %_sysconfdir/init.d/campsite %_sysconfdir/rc0.d/K50campsite
> ln -s %_sysconfdir/init.d/campsite %_sysconfdir/rc6.d/K50campsite
> scrollkeeper-update
> /sbin/service campsite start
>
> %preun
> /sbin/service campsite stop
>
> %postun
> rm -f %_sysconfdir/rc3.d/S95campsite
> rm -f %_sysconfdir/rc5.d/S95campsite
> rm -f %_sysconfdir/rc0.d/K50campsite
> rm -f %_sysconfdir/rc6.d/K50campsite
> scrollkeeper-update
>
> %files
> %campsitedir/
> %campsitedir/backup
> %config %campsiteetc/parser_conf.php
> %config %campsiteetc/vhost-template.conf
> %config %campsiteetc/install_conf.php
> %_bindir
> %_bindir/cli_script_lib.php
> %_bindir/create_instance
> %_bindir/backup_instance.php
> %_bindir/notifyevents
> %_bindir/campsite_server
> %_bindir/backup_instance
> %_bindir/smtp_wrapper
> %_bindir/restore_instance
> %_bindir/autopublish
> %_bindir/campsite_config
> %_bindir/create_instance.php
> %_bindir/campsitectl
> %_bindir/remove_instance.php
> %_bindir/remove_instance
> %_bindir/notifyendsubs
> %_bindir/restore_instance.php
> %_bindir/gather
> %_bindir/autopublish.php
>
> %campsitewww
> %campsitewwwcommon
> %campsitewwwcommon/*
>
> %campsitedir/instance
> %campsitedir/instance/database
> %campsitedir/instance/database/campsite-db.sql
> %campsitedir/instance/database/upgrade
> %campsitedir/instance/database/upgrade/*
> %_sysconfdir/cron.d/campsite_gather
> %_sysconfdir/cron.d/campsite_autopublish
> %_sysconfdir/cron.d/notifyendsubs
> %_sysconfdir/cron.d/notifyevents
> %_sysconfdir/init.d/campsite
> %_datadir/omf/campsite.omf
>
> %doc documentation/*
>
> %changelog
> * Wed Aug 10 2005 John Pye
> - Revised for Campsite 2.3.0
>
> * Wed Jun 22 2005 John Pye
> - Initial RPM release.

------------------------------------------
Posted to Phorum via PhorumMail

Campsite above 2.1 made huge changes to this and I would not change
anything on them. Please look at that, it worth to
Major changes:
Campsite is installed to /usr/local/campsite and that is it.
Campsite installs environment that is shared between instances
Instance is similar to previous campsite instalation
This way when campsite is being hosted, you just install campsite once
and for each hosting custommer you simply add new instance.
Port installs environment, instances admin has to manage himself.

I just add rc script to /usr/local/etc/rc.d and there is some change
in /var/cron/root that needs to be done yet, because if you delete
campsite package, I still do not clean crontab. The major problem is,
that crontab is edited through campsite internal install process that is
not controlled by port and therefore port has no idea about existance of
any cron records.
My idea is to patch campsite to disable the cron records install and
provide some inside port.

However there is still a problem with campsite cleaning:
I did not decided how to handle instances data (database, templates,
images, configurations). They are also not present in the time of
campsite install, so I cannot remove them at the time of uninstalling
port. Also this would make difficulties when upgrading between two
versions of ports, as it would delete instances, which is not what we
want.
Probably I will just write some messages directing admin how to behave
and what to clean.


On Thu, 2005-08-11 at 10:22 +0100, Ian Morrison wrote:
> /usr/local/share/campsite for instance templates and backup files
> /usr/local/bin for all executables
> /usr/local/etc/campsite for settings
> /usr/local/share/campsite/www-common for common WWW files
>
> last time i used capsite, it didn't virtualise very easily, so i'd
> imagine the default instance would go in either /usr/local/share/campsite/
> or /usr/local/www/campsite which you would then configure apache to
> serve. so /usr/local/www/campsite/html/look...
>

------------------------------------------
Posted to Phorum via PhorumMail

* John Pye [2005-08-11 13:04]:

> Out of curiosity, if Campsite conformed use the GNU Autotools build
> system, would this make your like easier? It would probably take a quite
> a bit to move over to Autotools, and especially with our move away from
> the C++ parser, it might be of dubious worth, however I imagine it would
> make cross-platform issues a lot easier to sort out.

I've wanted exactly this functionality from the second I used the bash
installer and tried to setup campsite to fit with my existing way of
doing things. There was even talk of mute part sponsoring richard@darq
doing the work, but it all kind of fizzled out. It would certainly make
cross-platform builds very straightforward, but if you're ditching the
c++ i'd agree that it's a lot of work for not a lot of benefit.

> Ian, thanks for the clear description in your mail.

No problem at all dude, happy to help.


ian
--
[darq# ian@darq.net] thoroughly modern misfit
[http://darq.net/#/] complete the puzzle : uid ---- day

------------------------------------------
Posted to Phorum via PhorumMail

--- John Pye wrote:
> The best idea is to use 'backup_instance campsite' then 'restore_instance -i
> campsite' after installing, I guess.
> Mugur: does doing this trigger the database update scripts?
No

> Out of curiosity, if Campsite conformed use the GNU Autotools build
> system, would this make your like easier? It would probably take a quite
> a bit to move over to Autotools, and especially with our move away from
> the C++ parser, it might be of dubious worth, however I imagine it would
> make cross-platform issues a lot easier to sort out.
It would take quite some work to rewrite the install scripts to use GNU
autotools and it doesn't worth the effort. We need to release 2.4 asap and it
will be the latest version that has these complicated install scripts. After
2.4 there will be no C++ in Campsite.

Mugur

> Ian, thanks for the clear description in your mail.
>
> JP
>
> Ondra Koutek wrote:
>
> >Campsite above 2.1 made huge changes to this and I would not change
> >anything on them. Please look at that, it worth to
> >Major changes:
> >Campsite is installed to /usr/local/campsite and that is it.
> >Campsite installs environment that is shared between instances
> >Instance is similar to previous campsite instalation
> >This way when campsite is being hosted, you just install campsite once
> >and for each hosting custommer you simply add new instance.
> >Port installs environment, instances admin has to manage himself.
> >
> >I just add rc script to /usr/local/etc/rc.d and there is some change
> >in /var/cron/root that needs to be done yet, because if you delete
> >campsite package, I still do not clean crontab. The major problem is,
> >that crontab is edited through campsite internal install process that is
> >not controlled by port and therefore port has no idea about existance of
> >any cron records.
> >My idea is to patch campsite to disable the cron records install and
> >provide some inside port.
> >
> >However there is still a problem with campsite cleaning:
> >I did not decided how to handle instances data (database, templates,
> >images, configurations). They are also not present in the time of
> >campsite install, so I cannot remove them at the time of uninstalling
> >port. Also this would make difficulties when upgrading between two
> >versions of ports, as it would delete instances, which is not what we
> >want.
> >Probably I will just write some messages directing admin how to behave
> >and what to clean.
> >
> >
> >On Thu, 2005-08-11 at 10:22 +0100, Ian Morrison wrote:
> >
> >
> >>/usr/local/share/campsite for instance templates and backup files
> >>/usr/local/bin for all executables
> >>/usr/local/etc/campsite for settings
> >>/usr/local/share/campsite/www-common for common WWW files
> >>
> >>last time i used capsite, it didn't virtualise very easily, so i'd
> >>imagine the default instance would go in either /usr/local/share/campsite/
> >>or /usr/local/www/campsite which you would then configure apache to
> >>serve. so /usr/local/www/campsite/html/look...
> >>
> >>
> >>
> >
> >
> >
> >
> >
>
>


__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

------------------------------------------
Posted to Phorum via PhorumMail

I think there is a script called "data-requires.sql" which includes a
multi-table UPDATE. MySQL 3.23 doesn't permit multi-table UPDATEs. To
patch it you would need to use a temporary table.I checked my database
and I didn't have any to which the update applied anyway, so I just left
it. Seriously though, only ONE SQL statement in all of campsite stops
you from running on MySQL 3.23 -- why did you decide to move to the new
version, you don't seem to be using the new features anywhere. Or is
ADODB hiding some of the issues from me, eg not attempting to perform
transactions, or something?

Mugur Rus wrote:

>If you can debug and let me know where the update crashes on MySQL 3.23 and
>maybe send me the patches I would commit them to SVN. Otherwise I don't think
>it's worth the effort to make it compatible with MySQL 3.23.
>
>Mugur
>
>--- John Pye wrote:
>
>
>>Note that MySQL version 4.0 is supposed to be required as well, but I've
>>managed to run everything except the upgrade scripts using mysql 3.23.
>>So my RPM only requires 3.23 for now, since 4.0 is not installed by
>>default on FC3.
>>JP
>>
>>Mugur Rus wrote:
>>
>>
>>
>>>>Most of the applications/libraries you need Campsite to run are listed in
>>>>INSTALL file. I would add:
>>>>- libxml 2.6.x or greater
>>>>- libstdc++ (STL - Standard Templates Library for C++)
>>>>- standard command line tools: pwd, ls, mkdir, chown, chmod, cat, cut,
>>>>
>>>>
>>grep,
>>
>>
>>>>cp, rm, locate, passwd, group, killall, convert
>>>>- PEAR
>>>>
>>>>
>>>>
>>>>
>>>Add iconv to command line tools.
>>>
>>>Mugur
>>>
>>>
>>>
>>>
>>>____________________________________________________
>>>Start your day with Yahoo! - make it your home page
>>>http://www.yahoo.com/r/hs
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Mail - Helps protect you from nasty viruses.
>http://promotions.yahoo.com/new_mail
>
>
>

------------------------------------------
Posted to Phorum via PhorumMail

Look to the future. 2.3 port is almost done and 2.4 should not be
changed much from 2.3 according to the port functionality - same
dependences, most of changes are done not as patch.
Once 2.4 is released, I will go through port and correct it, it should
not be too much work.
Sfter 2.4 you already mentioned, that we will move to PHP and install
scripts will change a lot. In my opinion at that point the only port
maintaining will be to test campsite and changing release numbers to
download proper sources.

Does it make sence?

Ondra

On Thu, 2005-08-11 at 07:36 -0700, Mugur Rus wrote:
> Then you'll have to maintain your patches for each Campsite version which is a
> lot of work. Why can't you give me the FreeBSD patches and see how can I
> include them so FreeBSD works and they don't break compatibility with other
> systems either.

------------------------------------------
Posted to Phorum via PhorumMail

At 22:19 15.08.2005, you wrote:
>What's the big deal about MySQL 3.23 anyway? 4.0 is out for quite some time
>now. You can report a bug, a low priority though.

isn't there a license issue with mysql 4? no more gpl / lgpl?

Micz Flor - micz@mi.cz

content and media development http://mi.cz
------------------------------------------------------------------
http://www.campware.org -- http://www.redall.de -- http://suemi.de
------------------------------------------------------------------

------------------------------------------
Posted to Phorum via PhorumMail

I think we're OK so long as we keep our code GPL
http://www.mysql.com/company/legal/licensing/opensource-license.html

Micz Flor wrote:

> At 22:19 15.08.2005, you wrote:
>
>> What's the big deal about MySQL 3.23 anyway? 4.0 is out for quite
>> some time
>> now. You can report a bug, a low priority though.
>
>
> isn't there a license issue with mysql 4? no more gpl / lgpl?
>
> Micz Flor - micz@mi.cz
>
> content and media development http://mi.cz
> ------------------------------------------------------------------
> http://www.campware.org -- http://www.redall.de -- http://suemi.de
> ------------------------------------------------------------------
>
>

------------------------------------------
Posted to Phorum via PhorumMail

> Agree with that. Mugur, did you see the patch file I sent to this list
> earlier on? I had to patch the restore_instance etc scripts again,
> something wrong with the number of arguments being passed between the
> bash and php scripts. I think Ondra has seen the same problem, so if you
> could incorporate his/my patch into the repository, that would be cool.
I applied your patches, these fixes will show up in 2.3.1

> Also in my patch is an extra variable in the make.env file, BUILD_ROOT,
> which is then used in all the "install:" sections in all the various
> Makefiles. This is the only safe way of installing with RPM given that
> the make.env file is used. This approach is backcompatible, since
> BUILD_ROOT is just set to empty string for non-RPM builds. I wonder if
> this BUILD_ROOT thing would be useful in DEB packaging as well?
Unfortunately I didn't have the time to test the whole patch, it's huge and I
can't apply it without testing it thoroughly.

Mugur


__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com

Thanks for the reminder. We are releasing Campsite 2.3.1 today and we
will release the packages templates also. We're testing them now.


Ana Nedic wrote:
> Hey,
>
> Boban and I are wondering what's going on with Package Templates that we
> sent. We didn't get any feedback information. I think that Paul is
> supposed to manage it.
>
>
>
> /Ana
>