<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html><head><title>nhc98 darcs repository</title></head>
<body bgcolor='#ffffff'>
<table><tr><td width=600>
<center>
<h1>darcs access to nhc98</h1>
</center>
<hr>
<p>
This page tells you how to get <a href="http://darcs.net">darcs</a>
access to the latest, most current, <em>nhc98</em> sources.
<p>
Note that we only store non-regenerable files in version control, so if
you don't already have a working Haskell compiler, you won't be able to
build from C sources using our repository.
<h3>Viewing the darcs repository on the web</h3>
<p>
If you don't want to download the sources, you can view the current
contents of the repository on the web
<a href="http://darcs.haskell.org/darcsweb/">here</a>.
<h3>Remote read-only access</h3>
<p>
Read-only access is available to anyone - there's no need to ask us
first. To get read-only access to our repository:
<ul>
<li> Obviously, you need to have the <em>darcs</em> command installed.
<li> <tt>darcs get --partial http://darcs.haskell.org/nhc98</tt>
<li> If you want the complete history, omit the <tt>-partial</tt> flag,
but be warned that the history is large, it will take a long time
to download, and may have errors on case-insensitive file systems
(e.g. Windows and MacOS X).
<li> The checked-out source tree will appear in a directory called
<tt>nhc98</tt>. You can rename this directory to whatever you
like, darcs won't mind.
<li> Change to that directory, and run the shell script <tt>sh start</tt>.
This will prepare the repository for use, by making various scripts
executable, downloading extra library packages, and so on.
<li> From then on, you can keep up with new changes in the central repo
by using <tt>darcs-all pull</tt>. You can even do your own
development in a detached fashion, using <tt>darcs record</tt> on
your own local repository.
</ul>
<p>
With read-only CVS access you can do anything except commit changes
back to the central repository. To submit patches to us, <tt>darcs
record</tt> them locally, then <tt>darcs send</tt>.
<h3>Using the checked-out tree</h3>
<p>
The first thing to do after checking out a fresh tree is <tt>sh
start</tt>, followed by <tt>./configure</tt>, and setting whatever
options you wish to use. It is always safe to re-run the
<tt>./configure</tt> script at any time - it will never leave your
configuration in an inconsistent state. The machine/OS combination is
always detected first so you can't re-use the wrong machine
configuration by mistake, and although previous options for a particular
machine are cached, they are always reported, and can be always
overridden on the command line.
<p>
Then, do a <tt>make</tt> with whatever targets you are interested
in: <tt>make help</tt> will give you a list of the common ones.
For instance, <tt>make basic</tt> gives you the standard compiler, and
<tt>make all</tt> gives you profiling and tracing variants in addition.
<h3>Tracking changes in the central repository</h3>
<p>
The log messages of all accepted darcs patches are sent to the mailing list
<tt>cvs-nhc98@haskell.org</tt>. If you wish to see who is making
changes, why, and and what they say about them, please do join this
list - see <a href="http://haskell.org/mailman/listinfo">
<tt>http://haskell.org/mailman/listinfo</tt></a> for further details.
<h3>Core developers - write-access to the repository</h3>
<p>
Core developers of Haskell have write-access to the central darcs
repository. All you need is an account on the machine
<tt>darcs.haskell.org</tt>.
<ul>
<li> You need to have <em>ssh</em> (secure shell) installed.
<li> The first time you commit a patch back to the repo, you will need
to specify where it is located:
<pre>darcs push darcs.haskell.org:/home/darcs/nhc98</pre>
<li> Thereafter, just use <tt>darcs push</tt> to commit patches.
</ul>
<p>
All the other instructions are the same.
<h3>Gaining write-access</h3>
<p>
To obtain write-access to darcs.haskell.org, you need to ask the
haskell.org maintainers - Simon Marlow <simonmar@haskell.org> or
Isaac Jones <ijones@galois.com> - for an account.
<p>
<hr>
<p>
The latest updates to these pages are available on the WWW from
<a href="http://www.haskell.org/nhc98/">
<tt>http://www.haskell.org/nhc98/</tt></a>
<p>
This page last modified: 11 July 2006<br>
<a href="http://www.cs.york.ac.uk/fp/">
York Functional Programming Group</a><br>
</td></tr></table>
</body></html>
|
