From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-apps@cygwin.com
Subject: Re: Testing ping for cygwin x86_64
Date: Wed, 23 Oct 2013 18:46:00 -0000 [thread overview]
Message-ID: <20131023184610.GA2378@calimero.vinschen.de> (raw)
In-Reply-To: <20131023174205.GA1619@ednor.casa.cgf.cx>
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
On Oct 23 13:42, Christopher Faylor wrote:
> On Wed, Oct 23, 2013 at 09:58:56AM +0200, Corinna Vinschen wrote:
> >On Oct 22 22:49, Balaji wrote:
> >> On Thu, Oct 17, 2013 at 11:54 AM, Corinna Vinschen wrote:
> >> > On Oct 17 10:17, Balaji wrote:
> >> [...]
> >> >> This being my first attempt at trying to possibly maintain a Cygwin
> >> >> package, I want make sure I'm doing the right thing. One odd thing is
> >> >> that all of the source code and Makefile are in the patch file. Also,
> >> >> am I free to convert the package to cygport/ditch the shell script
> >> >> etc. - I understand all that may typically be the maintainer's choice?
> >> >> Advance thanks for any advice from you seasoned veterans.
> >> >
> >> > Porting a package to cygport is highly appreciated, no worries. And of
> >> > course you are free to pack it in a cleaner fashion than the existing
> >> > package.
> >>
> >> One other question - I remember there was some discussion about noarch
> >> packages a while ago. Are there any rules for/against making something
> >> a noarch package. And the associated pros/cons - both from a
> >> maintainer and user perspective?
> >
> >Noarch packages are fine, but the packaging mechanism doesn't support
> >them the same way as in Linux distros. They still have to show up
> >twice, once in the 32 and once in the 64 bit release area.
>
> i.e., just like Linux distros do.
Well, kind of. OpenSuSE provides subdirectories i586/i686, x86_64, and
noarch for packages which are target-independent, which is neat.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-10-23 18:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 17:17 Balaji Venkataraman
2013-10-17 18:54 ` Corinna Vinschen
[not found] ` <CALgEz7oEJ0yyUhLmoyqVxvadXHLFPbr9WTPwAoV0mG1WETR4Rg@mail.gmail.com>
2013-10-23 5:49 ` Fwd: " Balaji Venkataraman
2013-10-23 7:59 ` Corinna Vinschen
2013-10-23 17:42 ` Christopher Faylor
2013-10-23 18:38 ` Achim Gratz
2013-10-23 19:26 ` Christopher Faylor
2013-10-23 18:46 ` Corinna Vinschen [this message]
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=20131023184610.GA2378@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).