| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
Bug fixed in 1.8.2:
* A (well known) portability bug slipped in the changes made to
install-sh in Automake 1.8.1. The broken install-sh would refuse to
install anything on Tru64.
* Fix install rules for conditionally built python files. (This never
really worked.)
Bug fixed in 1.8.1:
* Bugs introduced by 1.8:
- Fix Config.pm import error with old Perl versions (at least
5.005_03). One symptom is that aclocal could not find its macro
directory.
- Automake 1.8 used `mkdir -m 0755 -p --' to ensure that directories
created by `make install' are always world readable, even if the
installer happens to have an overly restrictive umask (e.g. 077).
This was a mistake and has been reverted. There are at least two
reasons why we must not use `-m 0755':
- it causes special bits like SGID to be ignored,
- it may be too restrictive (some setups expect 775 directories).
- Fix aclocal to honor definitions located in files which have been
m4_included manually. aclocal 1.8 had been updated to check
m4_included files for new requirements, but forgot that these
m4_included files can also provide new definitions.
Note that if you have such a setup, we recommend you get rid of
it. In the past, there was a reason to m4_include files manually:
aclocal used to duplicate entire M4 files into aclocal.m4, even
files that were distributed. Some packages were therefore
m4_including the distributed file directly, and playing some
tricks to ensure aclocal would not copy that file to aclocal.m4,
in order to limit the amount of duplication. Since aclocal 1.8.x
will precisely output m4_includes for local M4 files, we recommend
that you clean up your setup, removing all manual m4_includes and
letting aclocal output them.
- Output detailed menus in the Info version if the Automake manual,
so that Emacs can locate the indexes.
- configure.ac and configure were listed twice in DIST_COMMON (an
internal variable where Automake lists configury files to
distribute). This was harmless, but unaesthetic.
- Use `chmod a-w' instead of `chmod -w' as the latter honors umask.
This was an issue only in the Automake package itself, not in
its output.
- Automake assumed that all AC_CONFIG_LINKS arguments had the form
DEST:SRC. This was wrong, as some packages do
AC_CONFIG_LINKS($computedlinks). This version no longer abort in
that situation.
- Contrary to mkinstalldirs, $(mkdir_p) was expecting exactly one
argument. This caused two kinds of failures:
- Rules installing data in a conditionally defined directory
failed when that directory was undefined. In this case no
argument was supplied.
- `make installdirs' failed, because several directories were
passed to $(mkdir_p). This was an issue only on platform
were $(mkdir_p) is implemented with `install-sh -d'.
$(mkdir_p) as been changed to accept 0 or more arguments, as
mkinstalldirs did.
* Long-standing bugs:
- Fix an unexpected diagnostic occurring when users attempt
to override some internal variables that Automake appends to.
- aclocal now scans configure.ac for macro definitions (PR/319).
- Fix a portability issue with OSF1/Tru64 Make. If a directory
distributes files which are outside itself (this usually occurs
when using AC_CONFIG_AUX_DIR([../dir]) to use auxiliary files
from a parent package), then `make distcheck' fails due to an
optimization performed by OSF1/Tru64 Make in its VPATH handling.
(tests/subpkg2.test failure)
- Fix another portability issue with Sun and OSF1/Tru64 Make.
In a VPATH-build configuration, `make install' would install
nobase_ files to wrong locations.
- Fix a Perl `uninitialized value' diagnostic occurring when
automake complains that a Texinfo file does not have a
@setfilename statement.
- Erase config.status.lineno during `make distclean'. This file
can be created by config.status. Automake already knew about
configure.lineno, but forgot config.status.lineno.
- Distribute all files, even those which are built and installed
conditionally. This change affects files listed in conditionally
defined *_HEADERS and *_PYTHON variable (unless they are nodist_*)
as well as those listed in conditionally defined dist_*_DATA,
dist_*_JAVA, dist_*_LISP, and dist_*_SCRIPTS variables.
- Fix AM_PATH_LISPDIR to avoid \? in sed regular expressions; it
doesn't conform to POSIX.
- Normalize help strings for configure variables and options added
by Automake macros.
* Anticipation:
- Check for python2.4 in AM_PATH_PYTHON.
* Spurious failures in test suite:
- tests/libtool5.test, tests/ltcond.test, tests/ltcond2.test,
tests/ltconv.test: fix failures with CVS Libtool.
- tests/aclocal6.test: fix failure if autom4te.cache is disabled.
- tests/txinfo24.test, tests/txinfo25.test, tests/txinfo28.test:
fix failures with old Texinfo versions.
|
|
|
|
* New features
- Default source file names in the absence of a _SOURCES declaration
are made by removing any target extension before appending `.c', so
to make the libtool module `foo.la' from `foo.c', you only need to
do this:
lib_LTLIBRARIES = foo.la
foo_la_LDFLAGS = -module
For backward compatibility, foo_la.c will be used instead of
foo.c if this file exists or is the explicit target of a rule.
However -Wobsolete will warn about this deprecated naming.
- AR's `cru' flags are now set in a global ARFLAGS variable instead
of being hard-coded in each $(AR) invocation, so they can be
substituted from configure.ac. This has been requested by people
dealing with non-POSIX ar implementations.
- New warning option: -Woverride. This will warn about any user
target or variable definitions which override Automake
definitions.
- Texinfo rules back up and restore info files when makeinfo fails.
- Texinfo rules now support the `html' target.
Running this requires Texinfo 4.0 or greater.
`html' is a new recursive target, so if your package mixes
hand-crafted `Makefile.in's with Automake-generated
`Makefile.in's, you should adjust the former to support (or
ignore) this target so that `make html' recurses successfully. If
you had a custom `html' rule in your `Makefile.am', it's better to
rename it as `html-local', otherwise your rule will override
Automake's new rule (you can check that by running `automake
-Woverride') and that will stop the recursion to subdirectories.
Last but not least, this `html' rule is declared PHONY, even when
overridden. Fortunately, it appears that few packages use a
non-PHONY `html' rule.
- Any file which is m4_included from configure.ac will appear as a
configure and Makefile.in dependency, and will be automatically
distributed.
- The rules for rebuilding Makefiles and Makefile.ins will now
rebuild all Makefiles and all Makefile.ins at once when one of
configure's dependencies has changed. This is considerably faster
than previous implementations, where config.status and automake
were run separately in each directory (this still happens when you
change a Makefile.am locally, without touching configure.ac or
friends). Doing this also solves a longstanding issue: these
rebuild rules failed to work when adding new directories to the
tree, forcing you to run automake manually.
- For similar reasons, the rules to rebuild configure,
config.status, and aclocal.m4 are now defined in all directories.
Note that if you were using the CONFIG_STATUS_DEPENDENCIES and
CONFIGURE_DEPENDENCIES (formerly undocumented) variables, you
should better define them in all directories. This is easily done
using an AC_SUBST (make sure you prefix these dependencies with
$(top_srcdir) since this variable will appear at different
levels of the build tree).
- aclocal will now use `m4_include' instead of copying local m4
files into aclocal.m4. (Local m4 files are those you ship with
your project, other files will be copied as usual.)
Because m4_included files are automatically distributed, it means
for most projects there is no point in EXTRA_DISTing the list of
m4 files which are used. (You can probably get rid of
m4/Makefile.am if you had one.)
- aclocal will avoid touching aclocal.m4 when possible, so that
Autom4te's cache isn't needlessly invalidated. This behavior can
be switched off with the new `--force' option.
- aclocal now uses Autoconf's --trace to detect macros which are
actually used and will no longer include unused macros simply
because they where mentioned. This was often the case for macros
called conditionally.
- New options no-dist and no-dist-gzip.
- compile, depcomp, elisp-comp, install-sh, mdate-sh, mkinstalldirs,
py-compile, and ylwrap, now all understand --version and --help.
- Automake will now recognize AC_CONFIG_LINKS so far as removing created
links as part of the distclean target and including source files in
distributions.
- AM_PATH_PYTHON now supports ACTION-IF-FOUND and ACTION-IF-NOT-FOUND
argument. The latter can be used to override the default behavior
(which is to abort).
- Automake will exit with $? = 63 on version mismatch. (So does
Autoconf 2.58) missing knows this, and in this case it will
emulate the tools as if they were absent. Because older versions
of Automake and Autoconf did not use this exit code, this change
will only be useful in projects generated with future versions of
these tools.
- When using AC_CONFIG_FILES with multiple input files, Automake
generates the first ".in" input file for which a ".am" exists.
(Former versions would try to use only the first input file.)
- lisp_DATA is now allowed. If you are using the empty ELCFILES
idiom to disable byte-compilation of lisp_LISP files, it is
recommended that you switch to using lisp_DATA. Note that
this is not strictly equivalent: lisp_DATA will install elisp
files even if emacs is not installed, while *_LISP do not
install anything unless emacs is found.
- Makefiles will prefer `mkdir -p' over mkinstalldirs if it is
available. This selection is achieved through the Makefile
variable $(mkdir_p) that is set by AM_INIT_AUTOMAKE to either
`mkdir -m 0755 -p --', `$(mkinstalldirs) -m 0755', or
`$(install_sh) -m 0755 -d'.
* Obsolete features
- Because `mkdir -p' is available on most platforms, and we can use
`install-sh -d' when it is not, the use of the mkinstalldirs
script is being phased out. `automake --add-missing' no longer
installs it, and if you remove mkinstalldirs from your package,
automake will define $(mkinstalldirs) as an alias for $(mkdir_p).
Gettext 1.12.1 still requires mkinstalldirs. Fortunately
gettextize and autopoint will install it when needed. Automake
will continue to define the $(mkinstalldirs) and to distribute
mkinstalldirs when this script is in the source tree.
- AM_PROG_CC_STDC is now empty. The content of this macro was
merged in AC_PROG_CC. If your code uses $am_cv_prog_cc_stdc, you
should adjust it to use $ac_cv_prog_cc_stdc instead. (This
renaming should be safe, even if you have to support several,
versions of Automake, because AC_PROG_CC defines this variable
since Autoconf 2.54.)
- Some users where using the undocumented ACLOCAL_M4_SOURCES
variable to override the aclocal.m4 dependencies computed
(inaccurately) by older versions of Automake. Because Automake
now tracks configure's m4 dependencies accurately (see m4_include
above), the use of ACLOCAL_M4_SOURCES should be considered
obsolete and will be flagged as such when running `automake
-Wobsolete'.
* Bug fixes
- Defining programs conditionally using Automake conditionals no
longer leads to a combinatorial explosion. The following
construct used to be troublesome when used with dozens of
conditions.
bin_PROGRAMS = a
if COND1
bin_PROGRAMS += a1
endif
if COND2
bin_PROGRAMS += a2
endif
if COND3
bin_PROGRAMS += a3
endif
...
Likewise for _SOURCES, _LDADD, and _LIBADD variables.
- Due to implementation constraints, previous versions of Automake
proscribed multiple conditional definitions of some variables
like bin_PROGRAMS:
if COND1
bin_PROGRAMS = a1
endif
if COND2
bin_PROGRAMS = a2
endif
All _PROGRAMS, _LDADD, and _LIBADD variables were affected.
This restriction has been lifted, and these variables now
support multiple conditional definitions as do other variables.
- Cleanup the definitions of $(distdir) and $(top_distdir).
$(top_distdir) now points to the root of the distribution
directory created during `make dist', as it did in Automake 1.4,
not to the root of the build tree as it did in intervening
versions. Furthermore these two variables are now only defined in
the top level Makefile, and passed to sub-directories when running
`make dist'.
- The --no-force option now correctly checks the Makefile.in's
dependencies before deciding not to update it.
- Do not assume that make files are called Makefile in cleaning rules.
- Update .info files in the source tree, not in the build tree. This
is what the GNU Coding Standard recommend. Only Automake 1.7.x
used to update these files in the build tree (previous versions did
it in the source tree too), and it caused several problems, varying
from mere annoyance to portability issues.
- COPYING, COPYING.LIB, and COPYING.LESSER are no longer overwritten
when --add-missing and --force-missing are used. For backward
compatibility --add-missing will continue to install COPYING (in
`gnu' strictness) when none of these three files exist, but this
use is deprecated: you should better choose a license yourself and
install it once for all in your source tree (and in your code
management system).
- Fix ylwrap so that it does not overwrite header files that haven't
changed, as the inline rule already does.
- User-defined rules override automake-defined rules for the same
targets, even when rules do not have commands. This is not new
(and was documented), however some of the automake-generated
rules have escaped this principle in former Automake versions.
Rules for the following targets are affected by this fix:
clean, clean-am, dist-all, distclean, distclean-am, dvi, dvi-am,
info, info-am, install-data-am, install-exec-am, install-info,
install-info-am, install-man, installcheck-am, maintainer-clean,
maintainer-clean-am, mostlyclean, mostlyclean-am, pdf, pdf-am,
ps, ps-am, uninstall-am, uninstall-info, uninstall-man
Practically it means that an attempt to supplement the dependencies
of some target, as in
clean: my-clean-rule
will now *silently override* the automake definition of the
rule for this target. Running `automake -Woverride' will diagnose
all such overriding definitions.
It should be noted that almost all these targets support a *-local
variant that is meant to supplement the automake-defined rule
(See node `Extending' in the manual). The above rule should
be rewritten as
clean-local: my-clean-rule
These *-local targets have been documented since at least
Automake 1.2, so you should not fear the change if you have
to support multiple automake versions.
* Miscellaneous
- The Automake manual is now distributed under the terms of the GNU FDL.
- Targets dist-gzip, dist-bzip2, dist-tarZ, dist-zip are always defined.
- core dumps are no longer removed by the cleaning rules. There are
at least three reasons for this:
1. These files should not be created by any build step,
so their removal do not fit any of the cleaning rules.
Actually, they may be precious to the developer.
2. If such file is created during a build, then it's clearly a
bug Automake should not hide. Not removing the file will
cause `make distcheck' to complain about its presence.
3. Operating systems have different naming conventions for
core dump files. A core file on one system might be a
completely legitimate data file on another system.
- RUNTESTFLAGS, CTAGSFLAGS, ETAGSFLAGS, JAVACFLAGS are no longer
defined by Automake. This means that any definition in the
environment will be used, unless overridden in the Makefile.am or
on the command line. The old behavior, where these variables were
defined empty in each Makefile, can be obtained by AC_SUBSTing or
AC_ARG_VARing each variable from configure.ac.
- CONFIGURE_DEPENDENCIES and CONFIG_STATUS_DEPENDENCIES are now
documented. (The is not a new feature, these variables have
been there since at least Automake 1.4.)
|
|
Bugs fixed in 1.7.9:
* Fix install-strip to work with nobase_ binaries.
* Fix renaming of #line directives in ylwrap.
* Rebuild with Autoconf 2.59. (1.7.8 was not installable with pdksh.)
Bugs fixed in 1.7.8:
* Remove spurious blank lines in cleaning rules introduced in 1.7.7.
* Fix detection of Debian's install-info, broken since version 1.5.
(Debian bug #213524).
* Honor -module if it appears in AM_LDFLAGS (i.e., relax name checking)
This was only done for libfoo_LDFLAGS and LDFLAGS in previous versions.
Bugs fixed in 1.7.7:
* The implementation of automake's --no-force option is unreliable,
so this option is ignored in this version. A real fix will appear in
Automake 1.8. (Debian Bug #206299)
* AM_PATH_PYTHON: really check the whole list of interpreters if no
argument is given. (Bug #399)
* Do not warn about leading `_' in variable names, even with -Wportability.
* Support user redefinitions of TEXINFO_TEX.
* depcomp: support AIX Compiler version 6.
* Fix missing rebuilds during `make dist' with BSD make.
(Could produce tarballs containing out-of-date files.)
* Resurrect multilib support.
* Noteworthy manual updates:
- Extending aclocal: how to write m4 macros that won't trigger warnings
with Automake 1.8.
- A Shared Library: Rewrite and split into subsections.
|
|
|
|
|
|
|
|
* Fix depcomp's icc mode for ICC 7.1.
* Diagnose calls to AC_CONFIG_FILES and friends with not enough arguments.
* Fix maintainer-clean's removal of autom4te.cache in VPATH builds.
* Fix AM_PATH_LISPDIR to work with POSIXLY_CORRECT=1.
* Fix the location reported in some diagnostics related to AUTOMAKE_OPTIONS.
* Remove Latin-1 characters from elisp-comp.
* Update the manual's @dircategory to match the Free Software Directory.
|
|
|
|
Bugs fixed in 1.7.5:
* Update install-sh's license to remove an advertising clause.
(Debian bug #191717)
* Fix a bug introduced in 1.7.4, related to BUILT_SOURCE handling,
that caused invalid Makefile.ins to be generated.
* Make sure AM_MAKE_INCLUDE doesn't fail when a `doit' file exists.
* New FAQ entry: renamed objects.
Bugs fixed in 1.7.4:
* Tweak the TAGS rule to support Exuberant Ctags (in addition to
the Emacs implementation)
* Fix output of aclocal.m4 dependencies in subdirectories.
* Use `mv -f' instead of `mv' in fastdep rules.
* Upgrade mdate-sh to work on OS/2.
* Don't byte-compile elisp files when ELCFILES is set empty.
(this documented feature was broken by 1.7.3)
* Diagnose trailing backslashes on last line of Makefile.am.
* Diagnose whitespace following trailing backslashes.
* Multiple tests are now correctly supported in DEJATOOL. (PR/388)
* Fix rebuilt rules for AC_CONFIG_FILES([Makefile:Makefile.in:Makefile.bot])
Makefiles. (PR/389)
* `make install' will build `BUILT_SOURCES' first.
* Minor documentation fixes.
|
|
|
|
Bugs fixed in 1.7.3:
* Fix stamp files numbering (when using multiple AC_CONFIG_HEADERS).
* Query distutils for `pythondir' and `pythonexecdir', instead of
using an hardcoded path. This should allow builds on 64-bit
distributions that usually use lib64/ instead of lib/.
* AM_PATH_PYTHON will also search for python2.3.
* elisp files are now built all at once instead of one by one. Besides
incurring a speed-up, this is required to support interdependent elisp files.
* Fix some incompatibilities with upcoming perl-5.10.
* Properly quote AC_PACKAGE_TARNAME and AC_PACKAGE_VERSION when defining
PACKAGE and VERSION.
* depcomp fixes:
- dashmstdout and dashXmstdout modes: don't use `-o /dev/null', this
is troublesome with gcc and Solaris compilers.
- makedepend mode: work with Libtool.
- support for ICC.
* better support for unusual gettext setups, such as multiple po/ directories:
- Flag missing po/ and intl/ directories as warnings, not errors.
- Disable these warnings if po/ does not exist.
* Noteworthy manual updates:
- New FAQ chapter.
- Document how AC_CONFIG_AUX_DIR interacts with missing files.
(Debian Bug #39542)
- Document `AM_YFLAGS = -d'.
|
|
* Fix installation and uninstallation of Info files built in subdirectories.
* Do not run `./configure --with-included-gettext' during `make distcheck'
if AM_GNU_GETTEXT([external]) is used.
* Correctly uninstall renamed man pages.
* Do not strip escaped newline in variables defined in one condition
and augmented in another condition.
* Fix ansi2knr rules for LIBOBJS sources.
* Clean all known Texinfo index files, not only those which appear to
be used, because we cannot know wich indexes are used in included files.
(Debian Bug #168671)
* Honor only the first @setfilename seen in a Texinfo file.
* Treat "required file X not found" diagnostics as errors (exit status 1).
* Don't complain that a required file is not found when it is a Makefile
target.
* Don't use single suffix inference rules when building `.info'-less
Info files, for the sake of Solaris make.
* The `check' target now depends on `$(BUILT_SOURCES)'.
* Recognize multiple inference rules such as `.a.b .c.d:'.
* Warn about multiple inference rules when -Wportability is used.
* Fix building of deansified files from subdirectories.
* Add missing `fi' in the .c->.obj rules.
* Improve install-sh to work even when names contain spaces or certain
(but not all) shell metachars.
* Fix the following spurious failures in the test suite:
depcomp2.test, gnits2.test, gnits3.test, python3.test, texinfo13.test
* Noteworthy manual updates:
- Augment the section about BUILT_SOURCES.
- Mention that AM_PROG_CC_STDC is a relic that is beter avoided today.
|
|
Bugs fixed in 1.7.1:
* Honor `ansi2knr' for files built in subdirectories, or using per-targets
flags.
* Aclocal should now recognize macro names containing parentheses, e.g.
AC_DEFUN([AC_LANG_PREPROC(Fortran 90)], [...]).
* Erase *.sum and *.log files created by DejaGnu, during `make distclean'.
(Debian Bug#153697)
* Install Python files even if they were built. (PR/369)
* Have stamp-vti dependent upon configure instead of configure.ac, as the
version might not be defined in the latter. (PR/358)
* Reorder arguments passed to a couple of commands, so things works
when POSIXLY_CORRECT=1.
* Fix a regex that can cause Perl to segfault on large input.
(Debian Bug#162583)
* Fix distribution of packages that have some sources defined conditionally,
as in the `Conditional compilation using Automake conditionals' example
of the manual.
* Fix spurious test suite failures on IRIX.
* Don't report a required variable as undefined if it has been
defined conditionally for the "right" conditions.
* Fix cleaning of the /tmp subdirectory used by `make distcheck', in case
`make distcheck' fails.
* Fix distribution of included Makefile fragment, so we don't create
spurious directories in the distribution. (PR/366)
* Don't complain that a target lacks `.$(EXEEXT)' when it has it.
|
|
Does not conflict with automake14 package.
|
|
Changes:
* Versioned install support back-ported from 1.6
|
|
have been converted to USE_BUILDLINK2.
|
|
|
|
Summary of changes:
- removal of USE_GTEXINFO
- addition of mk/texinfo.mk
- inclusion of this file in package Makefiles requiring it
- `install-info' substituted by `${INSTALL_INFO}' in PLISTs
- tuning of mk/bsd.pkg.mk:
removal of USE_GTEXINFO
INSTALL_INFO added to PLIST_SUBST
`${INSTALL_INFO}' replace `install-info' in target rules
print-PLIST target now generate `${INSTALL_INFO}' instead of `install-info'
- a couple of new patch files added for a handful of packages
- setting of the TEXINFO_OVERRIDE "switch" in packages Makefiles requiring it
- devel/cssc marked requiring texinfo 4.0
- a couple of packages Makefiles were tuned with respect of INFO_FILES and
makeinfo command usage
See -newly added by this commit- section 10.24 of Packages.txt for
further information.
|
|
for 4 months!
While I'm here change the maintainer to packages@netbsd.org
|
|
|
|
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
|
|
|
|
|
|
|
|
|
|
Noted by Martti Kuparinen <martti.kuparinen@iki.fi> in PR 13792
|
|
|
|
Include a bugfix for lisp_LISP independently discovered by me that has
been pulled up to the automake-1-4 branch of automake cvs.
Changes are:
New in 1.4-p5:
* Allow AM_PROG_LIBTOOL again.
* Diagnose AC_CONFIG_HEADERS the same as AC_CONFIG_HEADER.
* Display distributed file list correctly in usage message.
* Allow numbers in macro names.
* Bugfixes.
New in 1.4-p4:
* Deal with configure.ac as well as configure.in -- this time for real!
* The version numbering system now allows three point version numbers,
such as 1.4.4, without thinking they are alpha release numbers.
New in 1.4-p3:
* Deal with configure.ac as well as configure.in.
* Don't complain if `version.texi' is included in multiple places.
New in 1.4-p2:
* Deal with AC_CONFIG_FILES from autoconf-2.50.
* Improvements to f77 support.
* DESTDIR now works for script targets.
* distcheck-hook works correctly.
New in 1.4-p1:
* The version numbering system now allows fork identifiers (such as
the p1 in this version of automake).
* Cope gracefully with various versions of libtool which may or may not
require ltconfig, ltcf-c.sh, ltcf-cxx.sh or ltcf-gcj.sh.
* Bugfixes.
|
|
|
|
|
|
+ move the patch digest/checksum values from files/patch-sum to distinfo
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It is used by many packages and was added to "pkgsrc/mk/NetBSD.pkg.dist"
a while ago.
|
|
|
|
|
|
|
|
exist, so remove the erroneous @exec statements (which wouldn't have
worked anyway).
|
|
- New, optional Makefile variable HOMEPAGE, specifies a URL for
the home page of the software if it has one.
- The value of HOMEPAGE is used to add a link from the
README.html files.
- pkglint updated to know about it. The "correct" location for
HOMEPAGE in the Makefile is after MAINTAINER, in that same
section.
|
|
|
|
|
|
|
|
Remove redundant (and sometimes erroneous) comments.
|
|
|
