From: Wayne Porter <wporter82@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] procps-ng
Date: Sun, 20 Mar 2016 21:47:00 -0000 [thread overview]
Message-ID: <CALsG8y1=doipaDAqiufpp9VxoAyi-CE+2D=jPmfY-Y5OYnVqrg@mail.gmail.com> (raw)
In-Reply-To: <CALsG8y3zRmPO5Ldzs0VH7C04Bd3BtmDQLXx8jFndmL1GMEgmgA@mail.gmail.com>
On Sun, Mar 20, 2016 at 2:00 PM, Wayne Porter <wporter82@gmail.com> wrote:
> On Sun, Mar 20, 2016 at 1:47 PM, Corinna Vinschen
> <corinna-cygwin@cygwin.com> wrote:
>> On Mar 18 17:25, Wayne Porter wrote:
>>> On Wed, Mar 16, 2016 at 1:51 PM, Yaakov Selkowitz <yselkowitz@cygwin.com> wrote:
>>> > On 2016-03-16 15:18, Wayne Porter wrote:
>>> >>
>>> >> Since I sent this package incorrectly the first time, I have
>>> >> repackaged it as procps-ng (it's correct name). The current stable
>>> >> build in debian is listed as 3.3.9, so that is the one that I ported.
>>> >> Please let me know if there is anything I'm leaving out or doing
>>> >> wrong.
>>> >
>>> >
>>> > Haven't tested the operation yet, but just looking at the build itself:
>>> >
>>> > * This needs to be broken up into procps-ng, libprocps3, and libprocps-devel
>>> > packages.
>>> >
>>> > * Along those lines, procps-ng needs to OBSOLETES procps (which also means
>>> > the first upload of this package needs to be coordinated with someone with
>>> > full sourceware access).
>>> >
>>> > * kill.exe and ps.exe conflict with commands of the same name in the
>>> > 'cygwin' package. In procps, these are renamed to prockill.exe and
>>> > procps.exe.
>>> >
>>> > * Your .cygport is missing HOMEPAGE, the SRC_URI is incorrect, and
>>> > DESCRIPTION has very long lines and improperly nested quotation marks. The
>>> > package is also built in $S instead of $B, resulting in a very dirty
>>> > .src.patch.
>>> >
>>> > Please fix these and repost.
>>> >
>>> > --
>>> > Yaakov
>>>
>>> Here is the package that obsoletes procps. I have repackaged it and
>>> added a few fixes
>>> that are specific for Cygwin based on changes to the latest version of
>>> procps. Let me
>>> know if there are any problems with this build.
>>>
>>> https://drive.google.com/folderview?id=0B6jD_6qfO1gMcVV2NXRjSGM1XzQ&usp=sharing
>>
>> Can you please provide direct links to the files, allowing to fetch
>> them via wget?
>>
>>
>> Thanks,
>> Corinna
>>
>> --
>> Corinna Vinschen Please, send mails regarding Cygwin to
>> Cygwin Maintainer cygwin AT cygwin DOT com
>> Red Hat
>
>
> I don't have a anywhere to upload the files to in order to allow wget
> access. That's the only reason I shared the files via google drive.
>
> Wayne
Ok, I have uploaded the files to the location here: http://wayneng.x10host.com/
Going to the url will show a list of all the files and you can wget
them directly
from there. Let me know if you have any issues downloading.
Wayne
next prev parent reply other threads:[~2016-03-20 21:30 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 [this message]
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
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='CALsG8y1=doipaDAqiufpp9VxoAyi-CE+2D=jPmfY-Y5OYnVqrg@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).