Re: [Firebird-docs] manual module

[Tilo M. <tm...@al...>]

Hi Paul

"Paul Vinkenoog" <pa...@vi...> schrieb im Newsbeitrag
news:Pin...@s4......
> > You are right, maybe we should move the zip one dir up?
>
> Then it would still create a wrongly named subdir and you'd have to
> move everything sideways instead of up...

So let's move the archives one dir up and point the users to the ReadMe file
;)

> Indeed "cvs add" is much more convenient if you have two zip archives
> instead of 1400 loose files, both text & bin :-)
>
> But I think if people want to help writing docs, the least we can do
> is give them a module that works out of the box.

I think we can't provide an out of the box solution. Remember Java, the env
variables, CVS, SSH, etc.

> Let's not forget that CVS may already be a hurdle for some people;
> also they may have to set up Java, and last but not least they may be
> totally unfamiliar with DocBook. If they go through all this trouble
> only to find themselves with a broken build, this may just be too
> much. But even for ourselves, it's nicer if a checkout "just works".

I handle it using two dirs, one in which I do all my CVS commands and
another dir in which I'm actually working. This way you are able to separate
all files which might be generated during the build process from those who
actually should go into CVS. So in your CVS dir there are the archives and
in the working dir reside the extracted files.

> I don't know if you have some smart CVS frontend that can add multiple
> files in one go; I'm pretty sure you don't feel like typing 1400 file
> names; and I know you have very little time. If you like I can write a
> little program or Perl script to traverse the dirs that the unzipped
> archive generates, adds them to CVS if necessary, and also adds the
> files they contain, deciding if they're txt or bin based on their
> extension. I can try it out on my local repository and send it to you
> if it works.

Take a look at "cvs import", this way you can bring in a whole bunch of
files.

> > Hopefully the purging of the obsolete files and dirs will take place
> > quite soon.
>
> I don't understand this. Doesn't "remove" work on SF? Once something
> is removed to the Attic, why do you care how soon it is purged? Or
> does it take a support request just to do a remove?

When something goes to the Attic you need to do a "cvs remove", but with
that huge amount of unneeded files it's much easier when SF do it.
BTW: Removing dirs from CVS is IMHO only an option for CVS admins.

> Greetings,
> Paul

Regards,
Tilo Muetze