Brian May [EMAIL PROTECTED] writes:
Russ Allbery wrote:
This seems to imply that you no longer have a file named rfc3454.txt? You
want to strip all the text out of that file except for the table, but
leave the table in the tree still named rfc3454.txt.
This would imply understanding
Russ Allbery wrote:
This seems to imply that you no longer have a file named rfc3454.txt? You
want to strip all the text out of that file except for the table, but
leave the table in the tree still named rfc3454.txt.
This would imply understanding what needs to be extracted. For
Hi,
On Mon, 2008-06-16 at 11:18 +1000, Brian May wrote:
I tried to upload what I have so far to Debian experimental so that
others can look at it (I hate being the sole maintainer of such a
complicated package). I think this is within the scope of experimental,
for anything that is
Russ Allbery wrote:
The text of the RFCs is copyrighted. The mapping tables in the RFCs
cannot be under US copyright law, and I believe copyright law in other
countries is similar. I'm guessing (I haven't looked closely) that what's
happening here is that the build process is generating code
Brian May [EMAIL PROTECTED] writes:
Is it possible to do this without messing around with Makefile.am, which
in turn will require rebuilding the automake stuff?
My first attempt didn't turn out so well:
make[3]: Leaving directory
Russ Allbery [EMAIL PROTECTED] writes:
Brian May [EMAIL PROTECTED] writes:
No responses? No one cares enough to comment? Lets see if a change in
subject helps.
Do the files created from the RFCs also have the same restrictive license
as the RFCs themselves?
The text of the RFCs is
No responses? No one cares enough to comment? Lets see if a change in
subject helps.
Do the files created from the RFCs also have the same restrictive
license as the RFCs themselves?
Brian May wrote:
Hello,
After messing around with autoconf/automake/libtool stuff for ages, I
eventually
Brian May [EMAIL PROTECTED] writes:
No responses? No one cares enough to comment? Lets see if a change in
subject helps.
Do the files created from the RFCs also have the same restrictive license
as the RFCs themselves?
The text of the RFCs is copyrighted. The mapping tables in the RFCs
Gervase Markham [EMAIL PROTECTED] writes:
Simon Josefsson wrote:
http://wiki.debian.org/NonFreeIETFDocuments
A useful thing to add to that page would be simple instructions on how
those authoring IETF documents could make them available under a
DFSG-free licence (presumably in parallel to
Simon Josefsson [EMAIL PROTECTED] writes:
Bug #390664 inspired me to look in source packages for IETF RFC/I-D's
too, and the situation seem to be more problematic. I've put a list
of packages in testing (as of a few days ago, my mirror is slow) that
appear to contain IETF RFC or I-D's at:
Simon Josefsson wrote:
http://wiki.debian.org/NonFreeIETFDocuments
A useful thing to add to that page would be simple instructions on how
those authoring IETF documents could make them available under a
DFSG-free licence (presumably in parallel to the IETF one) - perhaps
some sample
11 matches
Mail list logo
