[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-wget] Planning update to wget. Should I upstream it?

From: Tim Rühsen
Subject: Re: [Bug-wget] Planning update to wget. Should I upstream it?
Date: Thu, 23 Aug 2018 09:56:13 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1

Hi Richard,

On 08/22/2018 08:21 PM, Richard Thomas wrote:
> Hi, hope this is the correct way to do this.
> I want to be able to download a webpage and all its prerequisites and
> turn it into a multipart/related single file. Now, this requires
> identifying and changing URLs which, as most members of this list are
> no-doubt aware is a thorny problem. Fortunately, wget already does this
> as part of its -p and -k options. Unfortunately, though it's amazingly
> useful, it's difficult to use the output for what I want.
> So I am planning on adding a way to implement this functionality
> directly into wget. Either I'll rewrite the links and filenames so that
> it's easy to piece together a multipart/related file from what is spit
> out or I'll have wget generate the multipart/related file itself
> (probably the latter or maybe both).
> I was just wondering if I should bother trying to feed this back into
> the project if there's any interest. Also, any suggestions on ways I can
> make this as useful as possible are welcome.

Feedback into the project is what it lives on :-)

Your goal sounds interesting, what do you need it for ?

We are currently developing wget2 and decided that we maintain wget 1.x
but new development should go into wget2 only.

Please see https://gitlab.com/gnuwget/wget2 for further information.

To jump in quickly, examine src/wget.c, function _convert_links(). You
could copy&paste it and amend it to your needs. Then add a new option
(see src/options.c) and call the new function instead of _convert_links().

To contribute non-trivial work, you have to assign the copyright of your
code to the FSF. Here is the standard intro/howto :-)


We at GNU try to enforce software freedom through a Copyleft
license (GPL)[0]. However, to enforce the said license, someone needs to
take proactive action when violations are found. Hence, we assign the
copyrights of the code to the FSF allowing them to act against anyone
that violates the license of the code you have written.

We, the maintainers of GNU Wget hence hereby request that you assign
the copyrights of the previous contributions that you have made, and
any future contributions to the FSF.

Should you have any questions, please feel free to reply back to this
mail. We will be glad to answer them and help you out.

Once you are willing to sign the Copyright assignment documents, kindly
copy the text after the marker in this email, fill it out and send it to

[0]: https://www.gnu.org/licenses/why-assign.en.html
Please email the following information to address@hidden, and we
will send you the assignment form for your past and future changes.

Please use your full legal name (in ASCII characters) as the subject
line of the message.

[What is the name of the program or package you're contributing to?]

[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]

[Do you have an employer who might have a basis to claim to own
your changes?  Do you attend a school which might make such a claim?]

[For the copyright registration, what country are you a citizen of?]

[What year were you born?]

[Please write your email address here.]

[Please write your postal address here.]

[Which files have you changed so far, and which new files have you written
so far?]

With best Regards, Tim

Attachment: signature.asc
Description: OpenPGP digital signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]