No Description
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Alf Gaida 27bfdcd7f0 some changes in debian/$foo 4 years ago
debian some changes in debian/$foo refs #1355 4 years ago
doc initial commit 4 years ago
m4 initial commit 4 years ago
po initial commit 4 years ago
src initial commit 4 years ago
.gitignore some changes in debian/$foo refs #1355 4 years ago
ABOUT-NLS initial commit 4 years ago
AUTHORS initial commit 4 years ago
BUGS initial commit 4 years ago
COPYING initial commit 4 years ago
COPYING.DOC initial commit 4 years ago
ChangeLog initial commit 4 years ago
ChangeLog.pre-2.1 initial commit 4 years ago
INSTALL initial commit 4 years ago
Makefile.am initial commit 4 years ago
Makefile.in initial commit 4 years ago
NEWS initial commit 4 years ago
README initial commit 4 years ago
README.SVN initial commit 4 years ago
THANKS initial commit 4 years ago
TODO initial commit 4 years ago
UPGRADE initial commit 4 years ago
aclocal.m4 initial commit 4 years ago
config.guess initial commit 4 years ago
config.h.in initial commit 4 years ago
config.rpath initial commit 4 years ago
config.sub initial commit 4 years ago
configure initial commit 4 years ago
configure.ac initial commit 4 years ago
depcomp initial commit 4 years ago
install-sh initial commit 4 years ago
missing initial commit 4 years ago
mkinstalldirs initial commit 4 years ago
nano.spec initial commit 4 years ago
nano.spec.in initial commit 4 years ago

README.SVN

INSTRUCTIONS TO COMPILE AND INSTALL NANO CVS VERSIONS
=====================================================

GNU nano is available from SVN, but building this needs a bit more care
than the official stable and unstable tarballs.


Prerequisites
-------------

To successfully compile GNU nano from CVS, you'll need the following
packages:

- autoconf (version >= 2.54)
- automake (version >= 1.7)
- gettext (version >= 0.11.5)
- groff (version >= 1.12)
- texinfo (version >= 4.0)
- subversion (aka svn)
- ssh (with support for the SSH version 2 protocol)
- glib 2.x (if your system doesn't have vsnprintf(), which the configure
script will check for)
- make, gcc and the normal development libraries (curses or slang, etc.)

These should be available on your GNU mirror. Note that you'll need a
version of curses or slang with wide character support if you want nano
to use UTF-8.


Download the source
-------------------

To obtain the current nano development code (called 'trunk'), use the
following command. It will create a copy of the files in a subdirectory
of your current working directory called 'nano':

$ svn co svn://svn.savannah.gnu.org/nano/trunk/nano

If you want to download the stable SVN branch instead, use:

$ svn co svn://svn.savannah.gnu.org/nano/branches/nano_2_0_branch/nano


Generate the configure script
-----------------------------

Once you have the sources in the "nano" directory,

$ cd nano
$ ./autogen.sh

This will set up a configure script and a Makefile.in file.


Configure your build
--------------------

To configure your build, run the configure script from the nano source
directory:

$ ./configure [--add-options-here]


Build and install
-----------------

From the nano source directory, build the code with:

$ make

Then, once it's done compiling, run

$ make install

which should copy various files (i.e. the nano executable, the info and
man pages, and syntax highlighting pattern files) to their appropriate
directories.

If you're installing into the default install directory (/usr/local),
you'll need to run that "make install" command with root privileges.


Problems?
---------

Please submit any bugs in the SVN branch using the Savannah project's
bug tracker (https://savannah.gnu.org/bugs/?group=nano)