From: Wayne Porter <wporter82@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] procps-ng
Date: Tue, 22 Mar 2016 21:00:00 -0000 [thread overview]
Message-ID: <CALsG8y16-WqCzKgxPJ4WiAmCF+oEA6USxzHhY7e--9ohpxwv5Q@mail.gmail.com> (raw)
In-Reply-To: <CAGHJv4fo4fcKfzwN_Df0p6jHM0vApVUyhtru1B7q+Rm3LmmGFQ@mail.gmail.com>
On Tue, Mar 22, 2016 at 11:02 AM, Chris Sutcliffe <ir0nh34d@gmail.com> wrote:
> On 22 March 2016 at 13:43, Wayne Porter wrote:
>> On Tue, Mar 22, 2016 at 8:14 AM, Chris Sutcliffe wrote:
>>> Yes, the libprocps-ng4 and libprocgs-ng-devel directories are missing
>>> in the x86_64 directory. They are present in the i686 directory.
>>
>> wget requires that you end the url with a slash in order to download properly.
>>
>> wget -r -np http://wayneng.x10host.com/procps-ng-3.3.10-1/x86_64/
>> wget -r -np http://wayneng.x10host.com/procps-ng-3.3.10-1/i686/
>>
>> These 2 work, but remove the slash on the end and it will complain
>> that libprocps-ng4 is not a directory.
>
> Good catch, with the trailing slash all the files were downloaded.
>
> Cheers,
>
> Chris
>
> --
> Chris Sutcliffe
Ok, I just moved the man3 pages around to the libdev package. They
should hopefully be correct now.
--
Wayne Porter
next prev parent reply other threads:[~2016-03-22 18:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 20:18 Wayne Porter
2016-03-16 20:48 ` Warren Young
2016-03-16 20:51 ` Yaakov Selkowitz
2016-03-19 0:25 ` Wayne Porter
2016-03-20 20:55 ` Corinna Vinschen
2016-03-20 21:41 ` Wayne Porter
2016-03-20 21:47 ` Wayne Porter
2016-03-21 9:40 ` Corinna Vinschen
2016-03-21 10:54 ` Wayne Porter
2016-03-21 12:05 ` Corinna Vinschen
2016-03-21 13:06 ` Corinna Vinschen
2016-03-21 21:01 ` Wayne Porter
2016-03-22 12:32 ` Corinna Vinschen
2016-03-22 13:46 ` Marco Atzeri
2016-03-22 15:14 ` Corinna Vinschen
2016-03-22 15:16 ` Marco Atzeri
2016-03-22 16:03 ` Chris Sutcliffe
2016-03-22 18:06 ` Wayne Porter
2016-03-22 18:12 ` Chris Sutcliffe
2016-03-22 21:00 ` Wayne Porter [this message]
2016-03-24 13:29 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALsG8y16-WqCzKgxPJ4WiAmCF+oEA6USxzHhY7e--9ohpxwv5Q@mail.gmail.com \
--to=wporter82@gmail.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).