Re: Cover Texts in the automake documentation
* Ben Pfaff ([EMAIL PROTECTED]) wrote: > Eric Dorland <[EMAIL PROTECTED]> writes: > > > * Alexandre Duret-Lutz ([EMAIL PROTECTED]) wrote: > >> > >> Eric: > >> | Is there any way you might consider dropping the > >> | Front and Back Cover Texts requirements from the manual? > >> > >> Sorry, this is the FSF policy. Not my call. > > > > Could you please point out where the FSF have made this policy? > > http://www.gnu.org/prep/maintain/maintain.html#License-Notices > > Documentation files should have license notices also. Manuals > should use the GNU Free Documentation License. Here is an example > of the license notice to use after the copyright notice. Please > adjust the list of invariant sections as appropriate for your > manual. (If there are none, then say with no invariant sections.) > See GNU Sample Texts, for a full example in a Texinfo manual. > > Permission is granted to copy, distribute and/or modify this > document under the terms of the GNU Free Documentation > License, Version 1.2 or any later version published by the > Free Software Foundation; with the Invariant Sections being > "GNU General Public License", with the Front-Cover Texts > being ``A GNU Manual,'' and with the Back-Cover Texts as in > (a) below. A copy of the license is included in the section > entitled "GNU Free Documentation License". > > (a) The FSF's Back-Cover Text is: ``You are free to copy > and modify this GNU Manual. Buying copies from GNU > Press supports the FSF in developing GNU and promoting > software freedom.'' > > If the FSF does not publish this manual on paper, then omit the > last sentence in (a) that talks about copies from GNU Press. If > the FSF is not the copyright holder, then replace FSF with the > appropriate name. Darn. That is a *should* and not a *must*. But I'm guessing that since the copyright holder is listed as the FSF, getting this changed will basically be impossible. *Sigh*. Ok, time to pull this sucker apart. -- Eric Dorland <[EMAIL PROTECTED]> ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ --END GEEK CODE BLOCK-- signature.asc Description: Digital signature
Re: How to specify additional dependencies of files
Stepan Kasal wrote: This gives me ./my-test: command not found as automake seems to prepend every test with ./ (to make it be run by the shell). Oops, I apologize for my mistake. So it seems you need a wrapper script: TESTS = my-test check_PROGRAMS = test test_SOURCES = test.cpp my-test: test$(EXEEXT) ...commands to create myfile and create/touch my-test wrapper (Actually, the above example contains a redundancy, because all check_PROGRAMS are built before the TESTS are run. So either the prerequisite test$(EXEEXT) can be deleted, or check_PROGRAMS can be changed to EXTRA_PROGRAMS.) Hope my advices help you to find the solution, though they contain errors. ;-) Thank you, that seems to work so far!
Re: How to specify additional dependencies of files
Hello, On Mon, Apr 10, 2006 at 07:54:14PM +, Daniel Kraft wrote: > Stepan Kasal wrote: > >You need to create a phony target that does both; builds `test', creates > >`myfile', and perhaps runs it. > > > >What about something like: > > > >TESTS = my-test > >.PHONY: my-test > >check_PROGRAMS = test > >test_SOURCES = test.cpp > > > >my-test: test$(EXEEXT) myfile > > ./test -f myfile > > This gives me > ./my-test: command not found > as automake seems to prepend every test with ./ (to make it be run by > the shell). Oops, I apologize for my mistake. So it seems you need a wrapper script: TESTS = my-test check_PROGRAMS = test test_SOURCES = test.cpp my-test: test$(EXEEXT) ...commands to create myfile and create/touch my-test wrapper (Actually, the above example contains a redundancy, because all check_PROGRAMS are built before the TESTS are run. So either the prerequisite test$(EXEEXT) can be deleted, or check_PROGRAMS can be changed to EXTRA_PROGRAMS.) Hope my advices help you to find the solution, though they contain errors. ;-) Have a nice day, Stepan
Re: How to specify additional dependencies of files
Stepan Kasal wrote: You need to create a phony target that does both; builds `test', creates `myfile', and perhaps runs it. What about something like: TESTS = my-test .PHONY: my-test check_PROGRAMS = test test_SOURCES = test.cpp my-test: test$(EXEEXT) myfile ./test -f myfile This gives me ./my-test: command not found as automake seems to prepend every test with ./ (to make it be run by the shell).
Re: Cover Texts in the automake documentation
Eric Dorland <[EMAIL PROTECTED]> writes: > * Alexandre Duret-Lutz ([EMAIL PROTECTED]) wrote: >> >> Eric: >> | Is there any way you might consider dropping the >> | Front and Back Cover Texts requirements from the manual? >> >> Sorry, this is the FSF policy. Not my call. > > Could you please point out where the FSF have made this policy? http://www.gnu.org/prep/maintain/maintain.html#License-Notices Documentation files should have license notices also. Manuals should use the GNU Free Documentation License. Here is an example of the license notice to use after the copyright notice. Please adjust the list of invariant sections as appropriate for your manual. (If there are none, then say with no invariant sections.) See GNU Sample Texts, for a full example in a Texinfo manual. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with the Invariant Sections being "GNU General Public License", with the Front-Cover Texts being ``A GNU Manual,'' and with the Back-Cover Texts as in (a) below. A copy of the license is included in the section entitled "GNU Free Documentation License". (a) The FSF's Back-Cover Text is: ``You are free to copy and modify this GNU Manual. Buying copies from GNU Press supports the FSF in developing GNU and promoting software freedom.'' If the FSF does not publish this manual on paper, then omit the last sentence in (a) that talks about copies from GNU Press. If the FSF is not the copyright holder, then replace FSF with the appropriate name. -- On Perl: "It's as if H.P. Lovecraft, returned from the dead and speaking by seance to Larry Wall, designed a language both elegant and terrifying for his Elder Things to write programs in, and forgot that the Shoggoths didn't turn out quite so well in the long run." --Matt Olson
Re: How to specify additional dependencies of files
Hello, On Mon, Apr 10, 2006 at 02:48:44PM +, Daniel Kraft wrote: > In my automake Makefile I need a way to generate testfiles when the > corresponding test program is compiled. I have something like: > > check_PROGRAMS = test > test_SOURCES = test.cpp > > But I need a file created by make (i.e., a command executed which > creates it) when test is compiled. Is there a way to specify this? > > test: myfile > > Doesn't work, [...] ... and also isn't what you meant; `myfile' is not a prerequisite for building the program `test', right? You need to create a phony target that does both; builds `test', creates `myfile', and perhaps runs it. What about something like: TESTS = my-test .PHONY: my-test check_PROGRAMS = test test_SOURCES = test.cpp my-test: test$(EXEEXT) myfile ./test -f myfile HTH, Stepan Kasal
Re: Cover Texts in the automake documentation
Hi Eric, * Eric Dorland wrote on Mon, Apr 10, 2006 at 07:19:59AM CEST: > * Russ Allbery ([EMAIL PROTECTED]) wrote: > > > > There are other GNU packages with GFDL manuals that do not have > > Front and Back Cover Texts, so it's clearly not a mandatory policy. > > Can you point out specific examples of this? The GNU Libtool manual doesn't. Nor does the GNU M4 manual. Cheers, Ralf
Re: Cover Texts in the automake documentation
* Alexandre Duret-Lutz ([EMAIL PROTECTED]) wrote: > > Eric: > | Is there any way you might consider dropping the > | Front and Back Cover Texts requirements from the manual? > > Sorry, this is the FSF policy. Not my call. I am unable to find this policy. Looking here: http://www.gnu.org/prep/standards/html_node/License-for-Manuals.html#License-for-Manuals, it states manuals should use GFDL but does not say there need be invariant sections. Looking at the GFDL howto (http://www.gnu.org/copyleft/fdl-howto.html), it states: Is it required for the document to have invariant sections? No. It is perfectly acceptable for a document to have no invariant sections. Could you please point out where the FSF have made this policy? -- Eric Dorland <[EMAIL PROTECTED]> ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ --END GEEK CODE BLOCK-- signature.asc Description: Digital signature
Re: Cover Texts in the automake documentation
* Russ Allbery ([EMAIL PROTECTED]) wrote: > Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes: > > Eric: > > | Is there any way you might consider dropping the > > | Front and Back Cover Texts requirements from the manual? > > > Sorry, this is the FSF policy. Not my call. > > There are other GNU packages with GFDL manuals that do not have Front and > Back Cover Texts, so it's clearly not a mandatory policy. Unfortunately, Can you point out specific examples of this? > the rest of us aren't really in a position to talk to the right people to > get this changed, whereas the official Automake maintainers would be. > Could you try? -- Eric Dorland <[EMAIL PROTECTED]> ICQ: #61138586, Jabber: [EMAIL PROTECTED] 1024D/16D970C6 097C 4861 9934 27A0 8E1C 2B0A 61E9 8ECF 16D9 70C6 -BEGIN GEEK CODE BLOCK- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ --END GEEK CODE BLOCK-- signature.asc Description: Digital signature
Re: Cover Texts in the automake documentation
%% Russ Allbery <[EMAIL PROTECTED]> writes: ra> Alexandre Duret-Lutz <[EMAIL PROTECTED]> writes: >> Eric: >> | Is there any way you might consider dropping the >> | Front and Back Cover Texts requirements from the manual? >> Sorry, this is the FSF policy. Not my call. ra> There are other GNU packages with GFDL manuals that do not have ra> Front and Back Cover Texts, so it's clearly not a mandatory ra> policy. Unfortunately, the rest of us aren't really in a position ra> to talk to the right people to get this changed, whereas the ra> official Automake maintainers would be. Could you try? It's my understanding (and I'm in no way speaking for the FSF here) that if the manual is published by the FSF as a book, with an ISBN etc., it has to have these front and back cover texts. Those texts only exist in the printed forms of the manual (since the front and back covers referred to by the texts only exist in printed forms of the manual). However, I have no idea whether or not this is a mandatory requirement for all GNU packages with published manuals. -- --- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://make.paulandlesley.org "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
How to specify additional dependencies of files
Hi! In my automake Makefile I need a way to generate testfiles when the corresponding test program is compiled. I have something like: check_PROGRAMS = test test_SOURCES = test.cpp But I need a file created by make (i.e., a command executed which creates it) when test is compiled. Is there a way to specify this? test: myfile Doesn't work, as test has other dependencies as well (generated by automake). Yours, Daniel Kraft
