summaryrefslogtreecommitdiff
path: root/README-hacking
AgeCommit message (Collapse)Author
2012-01-01maint: update all copyright year number rangesJim Meyering
Run "make update-copyright".
2011-05-25doc: make README-hacking slightly more genericJim Meyering
* README-hacking: Remove a reference to "coreutils".
2011-05-23maint: README-hacking clarificationsKarl Berry
* README-hacking: Small getting-started clarifications.
2011-01-01maint: update all copyright year number rangesJim Meyering
Run "make update-copyright".
2010-07-04doc: Add advice about ChangeLogs and synchronizing submodulesPaul Eggert
* README-hacking: Update accordingly.
2010-02-25bootstrap: resynchronize from gnulibEric Blake
* gnulib: Update to latest. * bootstrap: Copy from gnulib/build-aux/bootstrap. * README-hacking: Describe how to use GNULIB_SRCDIR.
2010-01-01maint: update all FSF copyright year lists to include 2010Jim Meyering
Use this command: git ls-files | grep -v COPYING \ | xargs env UPDATE_COPYRIGHT_USE_INTERVALS=1 \ build-aux/update-copyright
2009-10-28doc: tell --enable-gcc-warnings users where to report problemsJim Meyering
* README-hacking: Add a caveat for --enable-gcc-warnings.
2009-10-20maint: issue warnings for more missing optional librariesPádraig Brady
* README-hacking: Suggest to use ./configure --quiet so that any warnings are easily noticed. * m4/gmp.m4 (cu_GMP): Warn if libgmp is not available. * m4/jm-macros.m4 (coreutils_MACROS): Normalize the libcap warning. * m4/xattr.m4 (gl_FUNC_XATTR): Warn if libattr is not available.
2009-08-25maint: remove Local Variables: indent-tabs-mode: nil from all sourcesJim Meyering
* src/getlimits.c: Likewise. * src/group-list.c: Likewise. * src/groups.c: Likewise. * src/mktemp.c: Likewise. * src/setuidgid.c: Likewise. * src/stdbuf.c: Likewise. * src/timeout.c: Likewise. * src/truncate.c: Likewise. * gl/lib/mbsalign.c: Likewise. * tests/test-lib.sh: Likewise. * bootstrap: Likewise. * README-hacking: Likewise.
2009-07-03maint: generalize the development prerequisites docsPádraig Brady
* README-hacking: Add a little more high level info and merge notes on specific developer prerequisites into README-prereq * README-prereq: Remove the Fedora 8 specific information and generalize the information to be applicable to any system.
2009-06-23doc: README-hacking tweakJim Meyering
* README-hacking: Move the "While building..." sentence down to where it belongs.
2009-06-20doc: typo fix in README-hackingJim Meyering
* README-hacking: Fix a typo. Don't make building from a git-cloned tree sound so hard.
2009-06-03doc: use newer URL for XZ utilsJim Meyering
* README-hacking: Use <http://tukaani.org/xz/> * README-prereq: Mention xz, not lzma.
2009-03-11maint: Document how to best to enable gcc warnings for developersPádraig Brady
* README-hacking: Mention --enable-gcc-warnings configure option * configure.ac: Don't scare developers away from using gcc warnings
2009-02-18add missing copyright datesEric Blake
* NEWS: Add 2009 to copyright. * README: Likewise. * README-hacking: Likewise. * TODO: Likewise. * doc/Makefile.am: Likewise. * m4/prereq.m4: Likewise. * src/nl.c: Likewise. * src/seq.c: Likewise. * tests/cp/cp-i: Likewise. * tests/install/install-C: Likewise. * tests/install/install-C-root: Likewise. * tests/install/install-C-selinux: Likewise. * tests/misc/seq: Likewise. * tests/mv/mv-n: Likewise.
2009-02-13maint: mention how to run a single test in HACKING docsPádraig Brady
* HACKING: Give an example of how to run a test in isolation. * README: Fix/simplify example for running a single test. * README-hacking: Reference the HACKING file.
2009-01-19build: use dist-xz, not dist-lzma, cont'dJim Meyering
* README-hacking: mention XZ utils * README-prereq: Add a FIXME comment.
2008-10-22Add better checks and docs for build toolsPádraig Brady
Prompted by a report from Ed Avis: <http://thread.gmane.org/gmane.comp.gnu.coreutils.bugs/14710> * README-hacking: Organise LZMA and Valgrind as as optional requirements rather than in their own sections. Mention bootstrap will now check tool versions. * README-prereq: Make a start on specific instructions for optaining build tools. Currently we just have notes for Fedora linux. * bootstrap.conf: Add the list of tools and versions required. * bootstrap: Add the logic to check for the required tools, and list all required tools and versions if any are missing.
2008-07-04* README-hacking: Update the section on LZMA.Jim Meyering
2008-01-22* README-hacking: Update to reflect existence of automake-1.10.1.Jim Meyering
2008-01-10* README-hacking: Add Git to the list of required tools.Jim Meyering
2007-10-24Doc improvements.Jim Meyering
* README-hacking: Prefer the no-hyphen variant of git commands, e.g., use "git pull" not "git-pull". Don't presume that the only way to read this document is via a prior git clone: provide instructions for cloning coreutils, too. * README-hacking: Add "cd automake" in build instructions. From Bob Proulx.
2007-10-23* README-hacking: Refer to LZMA Utils <http://tukaani.org/lzma/>.Jim Meyering
2007-10-22* README-hacking: Describe how to build with LZMA.Paul Eggert
2007-09-03README-hacking: Require rsync, rather than wget.Jim Meyering
2007-07-23Update all copyright notices to use the newer form.Jim Meyering
2007-07-10Change "version 2" to "version 3" in all copyright notices.Jim Meyering
2007-06-18* README-hacking: Don't mention Gzip 1.2.4, now that 1.3.12 is out.Jim Meyering
2007-06-13* README-hacking: List Gperf as a build-requirement, too.Jim Meyering
Reported by Steve Ward.
2007-05-15Generate a dozen test-related Makefile.am files at bootstrap-time.Jim Meyering
* README-hacking: Build-from-checkout now require Perl, too. * bootstrap: Now that these generated Makefile.am files are no longer under version control, they must be created at bootstrap time.
2007-02-20* README-hacking: Update to reflect that we now use git.Jim Meyering
2007-02-20Now that we use GIT, not cvs, rename README-cvs.Jim Meyering
* README-hacking: Renamed from... * README-cvs: ...this.
generated by cgit v1.2.3-70-g09d2 (git 2.47.1) at 2024-12-26 06:10:50 +0000