xref: /hello/
Name Date Size

..29-Nov-20194 KiB

.gitignoreH A D13-Aug-2017571

.gitmodulesH A D13-Aug-201775

.prev-versionH A D13-Aug-20175

AUTHORSH A D20-Jan-2019580

bootstrapH A D20-Jan-201932.8 KiB

bootstrap.confH A D20-Jan-20193.5 KiB

build-aux/H20-Jan-20194 KiB

cfg.mkH A D20-Jan-2019948

ChangeLog.OH A D20-Jan-201929.8 KiB

configure.acH A D22-Jan-20192.3 KiB

contrib/H20-Jan-20194 KiB

COPYINGH A D05-Oct-201734.3 KiB

doc/H20-Jan-20194 KiB

gnulib/H13-Aug-20174 KiB

lib/H13-Aug-20174 KiB

Makefile.amH A D20-Jan-20193.6 KiB

man/H20-Jan-20194 KiB

NEWSH A D20-Jan-20194.1 KiB

po/H20-Jan-20194 KiB

READMEH A D20-Jan-20193.4 KiB

README-devH A D20-Jan-20191.5 KiB

scripts/git-hooks/H13-Aug-20174 KiB

src/H09-Feb-20194 KiB

tests/H20-Jan-20194 KiB

THANKSH A D20-Jan-2019891

TODOH A D27-Sep-2017208

README

1This is the README file for the GNU Hello distribution.
2Hello prints a friendly greeting.  It also serves as a sample GNU
3package, showing practices that may be useful for GNU projects.
4
5  Copyright (C) 1992-2019 Free Software Foundation, Inc.
6
7  Copying and distribution of this file, with or without modification,
8  are permitted in any medium without royalty provided the copyright
9  notice and this notice are preserved.
10
11See the files ./INSTALL* for building and installation instructions.
12
13Primary distribution point: ftp://ftp.gnu.org/gnu/hello/
14 automatic redirection: https://ftpmirror.gnu.org/hello
15 list of mirrors for manual selection: https://www.gnu.org/prep/ftp.html
16
17Home page: https://www.gnu.org/software/hello/
18
19Developer page: https://savannah.gnu.org/projects/hello/
20- please file bug reports, patches and feature requests here if
21  possible (otherwise, feel free to use the mailing list)
22- significant contributions require a copyright assignment to the Free
23  Software Foundation. The maintainer will be happy to answer
24  questions about the process.
25
26Mailing list: bug-hello@gnu.org
27- please use this list for all discussion
28- archived at: https://lists.gnu.org/pipermail/bug-hello
29- anyone is welcome to join the list; to do so, visit
30  https://lists.gnu.org/mailman/listinfo/bug-hello
31
32Bug reports:
33 Please include enough information for the maintainers to reproduce the
34 problem.  Generally speaking, that means:
35- the contents of any input files necessary to reproduce the bug
36  and command line invocations of the program(s) involved (crucial!).
37- a description of the problem and any samples of the erroneous output.
38- the version number of the program(s) involved (use --version).
39- hardware, operating system, and compiler versions (uname -a).
40- unusual options you gave to configure, if any (see config.status).
41- anything else that you think would be helpful.
42
43Patching process:
44- All changes must be sent to mailing list.
45- Changes are reviewed by maintainers.
46- Maintainer does not review own changes.
47  * In case of single maintainer, or unresponsive co-maintainer, mailing
48    list subscribers may perform the review.
49- Review means either a patch approval, comments to author, or a reject.
50  * Approved patches are taken to upstream git.
51  * Commented patches will require work before they can be approved.
52    Comments can be untechnical, such as a change author must submit a
53    copyright assignment to FSF.
54  * Authors are encouraged to discontinue work with rejected changes, as
55    the reject is permanent.
56- Maintainers keep track of rejected changes so that developers can avoid
57  proposing the same in future.
58
59Patches are most welcome; if possible, please make them in git-am
60format, and include a suitable commit message.
61
62See README-dev for information on the development environment -- any
63interested parties are welcome.  If you're a programmer and wish to
64contribute, this should get you started.  If you're not a programmer,
65your help in writing test cases, checking the documentation against the
66implementation, translating the program strings to other languages,
67etc., would still be very much appreciated.
68
69The basic Hello algorithm was described by B.W. Kernighan and
70D.M. Ritchie.  The GNU implementation is substantially more complex, in
71order to be a canonical example of a GNU package.  Many people have
72contributed; please see the AUTHORS and ChangeLog files.
73
74GNU Hello is free software.  See the file COPYING for copying conditions.
75

README-dev

1This README.dev file describes the development environment.
2
3  Copyright (C) 2002-2019 Free Software Foundation, Inc.
4
5  Copying and distribution of this file, with or without modification,
6  are permitted in any medium without royalty provided the copyright
7  notice and this notice are preserved.
8
9The development sources are available through git  at Savannah:
10
11  https://savannah.gnu.org/git/?group=hello
12
13
14Autotools
15---------
16
17This distribution uses whatever versions of Automake, Autoconf and
18Gettext are listed in NEWS; usually the latest ones released.  If you
19are getting the sources from git (or change configure.ac), you'll
20need to have these tools installed to (re)build.  You'll also need
21help2man.  All of these programs are available from
22ftp://ftp.gnu.org/gnu.
23
24
25Building
26--------
27
28After getting the git sources, and installing the tools above, you
29can run
30
31  ./bootstrap
32
33to do a fresh build.  After that first time, running make should suffice.
34
35When modifying the sources, or making a distribution, more is needed, as
36follows:
37
38
39Gnulib
40------
41
42This distribution also uses Gnulib (https://www.gnu.org/software/gnulib)
43to share common files, stored as a submodule in git.
44
45
46Gettext
47-------
48
49When updating gettext, besides the normal installation on the system, it
50is necessary to run gettextize -f in this hierarchy to update the po/
51infrastructure.  After doing so, rerun gnulib-tool --import since
52otherwise older files will have been imported.  See the Gnulib manual
53for more information.
54