You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by David Crossley <cr...@indexgeo.com.au> on 2002/07/26 08:35:52 UTC
fully implement the bert skin
The new skin seems ready to become the default skin
for building the Forrest site and the local docs.
Recently a parameter use.skin=bert was added to build.xml
to make the 'bert' skin the default. However we need to
do a bit more than that. The resources/skins/bert/* needs
to replace resources/skins/forrest-site/*
How do we do that while retaining the CVS history of both, yet
not leaving old directories lying around which may confuse?
Is there anything in the old 'forrest-site' that we want to
keep? It seems not.
--David
Re: fully implement the bert skin
Posted by David Crossley <cr...@indexgeo.com.au>.
Steven Noels wrote:
> David Crossley wrote:
> > David Crossley wrote:
> >>However, there is one strange thing ...
> >>I expected that "cvs update -P xml-forrest" would remove
> >>the skins/bert from the local working copy, but it does not.
> >>--David
> >
> >
> > Did anyone else have the same trouble? When you updated,
> > was the empty "bert directory" properly removed from your
> > working copy?
> > --David
>
> no problems here - using "cvs -q update -dP"
Thanks, good to hear that. Mine is fixed now too. There
was an invisible local backup file of book2menu.xsl that
was preventing the -Prune ... fixed now.
--David
Re: fully implement the bert skin
Posted by Steven Noels <st...@outerthought.org>.
David Crossley wrote:
> David Crossley wrote:
>>However, there is one strange thing ...
>>I expected that "cvs update -P xml-forrest" would remove
>>the skins/bert from the local working copy, but it does not.
>>--David
>
>
> Did anyone else have the same trouble? When you updated,
> was the empty "bert directory" properly removed from your
> working copy?
> --David
no problems here - using "cvs -q update -dP"
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
stevenn@outerthought.org stevenn@apache.org
Re: fully implement the bert skin
Posted by David Crossley <cr...@indexgeo.com.au>.
David Crossley wrote:
> As you would have seen from the commit messages, i have
> patched the original "forrest-site" skin to reflect the
> changes from the new "bert" skin. So now forrest-site is
> the default again.
>
> The bert skin has been "cvs remove", so if you have any
> outstanding changes then please add them to the forrest-site
> skin instead.
>
> However, there is one strange thing ...
> I expected that "cvs update -P xml-forrest" would remove
> the skins/bert from the local working copy, but it does not.
> --David
Did anyone else have the same trouble? When you updated,
was the empty "bert directory" properly removed from your
working copy?
--David
Re: fully implement the bert skin
Posted by David Crossley <cr...@indexgeo.com.au>.
As you would have seen from the commit messages, i have
patched the original "forrest-site" skin to reflect the
changes from the new "bert" skin. So now forrest-site is
the default again.
The bert skin has been "cvs remove", so if you have any
outstanding changes then please add them to the forrest-site
skin instead.
However, there is one strange thing ...
I expected that "cvs update -P xml-forrest" would remove
the skins/bert from the local working copy, but it does not.
--David
Re: fully implement the bert skin
Posted by Bert Van Kets <be...@vankets.com>.
At 08:49 26/07/2002 +0200, you wrote:
>David Crossley wrote:
>
>>The new skin seems ready to become the default skin
>>for building the Forrest site and the local docs.
>>Recently a parameter use.skin=bert was added to build.xml
>>to make the 'bert' skin the default. However we need to
>>do a bit more than that. The resources/skins/bert/* needs
>>to replace resources/skins/forrest-site/*
>>How do we do that while retaining the CVS history of both, yet
>>not leaving old directories lying around which may confuse?
>
>I was thinking of copying files over from the bert skin to
>forrest-site, and removing those use.skin=bert from places and
>cvs-removing the bert directory afterwards...
>
>we could swap things repository-side but I'm not too keen on that
>
>>Is there anything in the old 'forrest-site' that we want to
>>keep? It seems not.
>
>not that I know of.
I confirm this. I started creating the Bert skin using the files in the
Forrest skin directory. So everything that *was* in there is in the Bert
skin too. Provided it's not updated yet of course.
Bert
>Regards,
>
></Steven>
>--
>Steven Noels http://outerthought.org/
>Outerthought - Open Source, Java & XML Competence Support Center
>stevenn@outerthought.org stevenn@apache.org
Re: fully implement the bert skin
Posted by Steven Noels <st...@outerthought.org>.
David Crossley wrote:
> The new skin seems ready to become the default skin
> for building the Forrest site and the local docs.
>
> Recently a parameter use.skin=bert was added to build.xml
> to make the 'bert' skin the default. However we need to
> do a bit more than that. The resources/skins/bert/* needs
> to replace resources/skins/forrest-site/*
>
> How do we do that while retaining the CVS history of both, yet
> not leaving old directories lying around which may confuse?
I was thinking of copying files over from the bert skin to forrest-site,
and removing those use.skin=bert from places and cvs-removing the bert
directory afterwards...
we could swap things repository-side but I'm not too keen on that
> Is there anything in the old 'forrest-site' that we want to
> keep? It seems not.
not that I know of.
Regards,
</Steven>
--
Steven Noels http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
stevenn@outerthought.org stevenn@apache.org