Ok, after I've not established the project environment for us, I've now spent
two days in front of Photoshop and WML and created the (hopefully) final
website. The major goals were:
1. All pages are generated out of a single template file and
this way produce a consistent look and feel over t
In article <[EMAIL PROTECTED]> you wrote:
> Ok, after I've not established the project environment for us, I've now spent
^^^
now! ;-)
Ralf S. Engelschall
[EMAIL PROTECTED]
In article <[EMAIL PROTECTED]> you wrote:
>[...]
> 1. All pages are generated out of a single template file and
>this way produce a consistent look and feel over the whole website. After
>we've finally comitted the website to CVS' openssl-web/ sub-repository one
>can edit it with an
What are we going to do about them? They are currently slapped on the
end of Makefile.ssl in the traditional way, but of course this causes a
problem with CVS.
Developing without them is a bugger, of course, so I don't consider that
to be an option.
Arrange things so Makefile is a copy of Makefi
While I'm currently on the way creating the first cut of a real documentation
set, I recognized that the stuff under doc/ is really a horrible mess, 80%
obsolete and more a joke than everything else. So my idea is to assemble all
the various .doc files into a single doc/ssleay.txt file. This way
Ben Laurie wrote:
>
> What are we going to do about them? They are currently slapped on the
> end of Makefile.ssl in the traditional way, but of course this causes a
> problem with CVS.
>
> Developing without them is a bugger, of course, so I don't consider that
> to be an option.
>
> Arrange t
Dr Stephen Henson wrote:
>
> Ben Laurie wrote:
> >
> > What are we going to do about them? They are currently slapped on the
> > end of Makefile.ssl in the traditional way, but of course this causes a
> > problem with CVS.
> >
> > Developing without them is a bugger, of course, so I don't conside
Better change the subject...
Ben Laurie wrote:
>
>
> Isn't that how its done already? But anyway, that wasn't what I meant -
> I mean how do we deal with the result of doing a "make depend", which
> alters all the Makefiles...
>
No that isn't what it does already. What it does is to copy the
