README.hacking missing

G’day,

FYI: The inofficial release installs ChangeLog, README and attempts to
install
README.hacking, which doesn’t exist in the tarball. It also crjeates an
empty
directory share/doc/gnuradio/html

BTW: Is there any point at all to install these files if a user decided
to
disable the creation of all other documents (e.g those created by
doxygen,
latex and friends)?

Just curious.

cheerio Berndt

On Thu, 2006-11-09 at 23:52 +1030, Berndt Josef W. wrote:

FYI: The inofficial release installs ChangeLog, README and attempts to install
README.hacking, which doesn’t exist in the tarball.

Is this while using pkgsrc? You’re correct, the README.hacking in the
root of the tree is not put into the release tarball, and the Makefile’s
don’t reference it, so I’m not sure what would be trying to install it.

BTW: Is there any point at all to install these files if a user decided to
disable the creation of all other documents (e.g those created by doxygen,
latex and friends)?

Which specific files are you referring to here?

Nothing like cutting a release to bring out the post-release bugs…


Johnathan C., AE6HO
Corgan Enterprises LLC
[email protected]

G’day,

Below is a partial log documenting the installation of the files in
question:

gmake[3]: Entering directory
/usr/pkgsrc/ham/gnuradio-core/work/gnuradio-3.0.1/gnuradio-core/doc' mkdir -p html gmake[4]: Entering directory/usr/pkgsrc/ham/gnuradio-core/work/gnuradio-3.0.1/gnuradio-core/doc’
gmake[4]: Nothing to be done for install-exec-am'. /usr/bin/install -d /usr/pkg/share/doc/gnuradio-3.0.1 /usr/bin/install -c -o root -g wheel -m 444 ../../README /usr/pkg/share/doc/gnuradio-3.0.1 /usr/bin/install -c -o root -g wheel -m 444 ../../README.hacking /usr/pkg/share/doc/gnuradio-3.0.1 install: ../../README.hacking: stat: No such file or directory /usr/bin/install -c -o root -g wheel -m 444 ../../ChangeLog /usr/pkg/share/doc/gnuradio-3.0.1 cp -r html /usr/pkg/share/doc/gnuradio-3.0.1 gmake[4]: Leaving directory/usr/pkgsrc/ham/gnuradio-core/work/gnuradio-3.0.1/gnuradio-core/doc’
g

The Makefile does make reference to it:

barossa: {100} grep README.hacking gnuradio-core/doc/*
gnuradio-core/doc/Makefile.am: @for i in $(top_srcdir)/README
$(top_srcdir)/README.hacking $(top_srcdir)/ChangeLog; do
gnuradio-core/doc/Makefile.am: @for i in README README.hacking
ChangeLog; do

gnuradio-core/doc/Makefile.in: @for i in $(top_srcdir)/README
$(top_srcdir)/README.hacking $(top_srcdir)/ChangeLog; do
gnuradio-core/doc/Makefile.in: @for i in README README.hacking
ChangeLog; do
\

gnuradio-core/doc/Makefile defines the following after running
configure:

gnuradio-core/doc/Makefile:
install-data-local:
$(mkinstalldirs) $(DESTDIR)$(docdir)
@for i in $(top_srcdir)/README $(top_srcdir)/README.hacking
$(top_srcdir)/ChangeLog; do
echo “$(INSTALL_DATA) $$i $(DESTDIR)$(docdir)”;
$(INSTALL_DATA) $$i $(DESTDIR)$(docdir);
done
cp -r html $(DESTDIR)$(docdir)
[…]

It isn’t related to pkgsrc other then it wasn’t noted by anyone. I’m
aware of
it now since the pkgsrc framework provides a mechanism that is used to
deinstall packages. It will issue warnings on attempts of
installing/deinstalling files that don’t exist.

The creation and installation of documentation created by doxygen and
tools
that depend on it is disabled by default (–enable-doxygen=no). I don’t
believe that a user choosing not to install gnuradio documentation cares
much
about the README* and ChangeLog files, especially since these are more
relevant to the decision making processes prior to the installation.

IMHO, it his doesn’t need to be fixed prior to the current release if it
is
too much of a pain to do since it won’t have any impact on the
performance of
GNU Radio and it has been like this for possibly a long time.

FYI: A installation log for gnuradio-core can be found on:

ftp://ftp.netbsd.org/pub/NetBSD/misc/wulf/gnuradio-core.log

cheerio Berndt

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs