[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Split INSTALL -> INSTALL.Unix and INSTALL.Windows ?

From: Max Bowsher <maxb1_at_ukf.net>
Date: 2005-11-28 14:38:04 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Sweet wrote:
> Max Bowsher wrote:
>
>> The INSTALL file is currently extremely large, and intermingles Unix and
>> Windows instructions in a way which is not ideal, either for the users
>> reading it, or for the people trying to maintain the document.
>>
>> Anyone have any objections to me splitting the INSTALL file into two
>> separate documents?
>
>
> One comment on this proposal - it would probably make sense to
> separate the Windows instructions into a separate file, but leave
> the UNIX/Linux instructions in "INSTALL". Similarly, you can add
> Novell, AS/400, etc. variations as needed, but the main file shows
> the common stuff with pointers to the others as needed.
>
> This is done with many other projects with good results...

I like this. It was in fact, my first thought.

I was slightly concerned about treating Windows as a second class
platform, but I guess this wouldn't necessarily be the case, given that
INSTALL is a traditional Unix/Linux name.

Perhaps we could keep the Unix/Linux instructions in 'INSTALL', and move
the Windows build instructions to a more Windows-like name, for example
'Windows-Build.txt'.

Best of both worlds, do you think?

Max.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Cygwin)

iD8DBQFDiwg8fFNSmcDyxYARAmjzAKDcGwbIbYEcp3f0+vVOOHiJflyOjwCgt52U
P7cCx7MoqAfMTPddR/BQcXw=
=SDsh
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 28 14:44:26 2005

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.