phpgroupware-developers
[Top][All Lists]
Advanced

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

Re: [phpGroupWare-developers] svn structure : idea


From: Dave Hall
Subject: Re: [phpGroupWare-developers] svn structure : idea
Date: Wed, 19 Dec 2007 14:54:48 +1100

On Tue, 2007-12-18 at 20:32 -0600, Chris Weiss wrote:
> should I go dig out the arguments for including cvs dirs in the
> tarballs in the first place  or do we need to have the whole
> discussion again?
> 
> to sum it up, it's less about version control and more about speed of
> applying updates and easy preservation of minor customizations.  more
> like an update/patching engine than version control

CVS/ and .svn are quite different.

SVN stored a lot of stuff in .svn (including a copy of every file which
has been checked out).  This will mean that we are shipping 100M+
releases, just so people can patch easily.

I think if people are hacking on phpgw - for the project or privately,
they should be able to use svn.

For an end user with shared hosting downloading a nightly build tarball
and ftp'ing to their hosting is easier than trying to explain svn to
them.

The discussion in the context of cvs and svn are very different.

Cheers

Dave

> 
> On Dec 18, 2007 5:34 PM, Dave Hall <address@hidden> wrote:
> >
> > On Tue, 2007-12-18 at 07:41 -0600, Chris Weiss wrote:
> > > how will affect updating stable installs?
> >
> > Stable installs still currently use CVS.  We may or may not do another
> > stable release, but this is unlikely.
> >
> > I think we should drop the .svn dirs from official and nightly build
> > releases.  version control is for developers, not end users.
> >
> > Cheers
> >
> > Dave
> >
> >
> > >
> > > On Dec 17, 2007 3:41 PM, Maat <address@hidden> wrote:
> > > > Hi all,
> > > >
> > > > Now we have svn we could use it to have an organization easier to use :
> > > >
> > > > -- one repository (with trunk/tags/branches) for core structure (with at
> > > > least phpgwapi, setup, admin, preferences, calendar and perhaps other
> > > > core parts inside) so that one svn checkout with no need to change or
> > > > move things brings a working phpgroupware instance
> > > > -- one repository (with trunk/tags/branches) for each "non core" module
> > > >
> > > > => that would be easier to start playing with phpgroupware source
> > > >
> > > > what d'you think of that ?
> > > >
> > > > maat
> > > >
> > > > --
> > > > In a world without walls or fences, there would be no need for windows 
> > > > or gates...
> > > >
> > > >
> > > > _______________________________________________
> > > >
> > > > phpGroupWare-developers mailing list
> > > > address@hidden
> > > > http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
> > > >
> > >
> > >
> > > _______________________________________________
> > > phpGroupWare-developers mailing list
> > > address@hidden
> > > http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
> > --
> > Dave Hall (aka skwashd)
> > API Coordinator
> > phpGroupWare
> > e address@hidden
> > w phpgroupware.org
> > j address@hidden
> > sip address@hidden
> >        _            ____                    __        __
> >  _ __ | |__  _ __  / ___|_ __ ___  _   _ _ _\ \      / /_ _ _ __ ___
> > | '_ \| '_ \| '_ \| |  _| '__/ _ \| | | | '_ \ \ /\ / / _` | '__/ _ \
> > | |_) | | | | |_) | |_| | | | (_) | |_| | |_) \ V  V / (_| | | |  __/
> > | .__/|_| |_| .__/ \____|_|  \___/ \__,_| .__/ \_/\_/ \__,_|_|  \___|
> > |_|         |_|                         |_|Web based collaboration platform
> >
> >
> >
> >
> >
> > _______________________________________________
> > phpGroupWare-developers mailing list
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
> >
> 
> 
> _______________________________________________
> phpGroupWare-developers mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/phpgroupware-developers
-- 
Dave Hall (aka skwashd)
API Coordinator
phpGroupWare
e address@hidden
w phpgroupware.org
j address@hidden
sip address@hidden
       _            ____                    __        __             
 _ __ | |__  _ __  / ___|_ __ ___  _   _ _ _\ \      / /_ _ _ __ ___ 
| '_ \| '_ \| '_ \| |  _| '__/ _ \| | | | '_ \ \ /\ / / _` | '__/ _ \
| |_) | | | | |_) | |_| | | | (_) | |_| | |_) \ V  V / (_| | | |  __/
| .__/|_| |_| .__/ \____|_|  \___/ \__,_| .__/ \_/\_/ \__,_|_|  \___|
|_|         |_|                         |_|Web based collaboration platform






reply via email to

[Prev in Thread] Current Thread [Next in Thread]