From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin-apps@cygwin.com
Subject: Re: [ITA] units
Date: Wed, 26 Apr 2017 02:59:00 -0000 [thread overview]
Message-ID: <e65a0c0b-737e-2d10-b5c9-ef1ee5d6f99d@SystematicSw.ab.ca> (raw)
In-Reply-To: <e0dfcba3-ad13-ff05-6128-02cecc66a67e@cygwin.com>
On 2017-04-25 20:25, Yaakov Selkowitz wrote:
> On 2017-04-25 17:42, Brian Inglis wrote:
>> As a long time user of Cygwin and units, both professionally and
>> personally, I noticed a new release of units 2.14 was available
>> but the package is orphaned.
>
> I have been nominally maintaining it anyway, but you're welcome to
> take it.
One less thing on your plate - but your call.
>> I built and installed the new release for myself, and thought I'd
>> like to make it available to the community, so would like to adopt
>> the package units.
>> I've had no problems downloading the prvious source, bumping the
>> cygport version, building, testing, installing, and using the new
>> release.
>
> That is a good start, but:
>
>> units.cygport
>> units-2.14-1.hint
>> units-2.14-1.tar.xz
>> units-2.14-1-src.tar.xz
>> units-debuginfo-2.14-1.hint
>> units-debuginfo-2.14-1.tar.xz
>
> This is the build from only one architecture. Each archful package
> needs to be built for each of x86 (32-bit) and x86_64 (64-bit). Are
> you set up to build both?
Yes - I still upgrade x86 infrequently.
>> I've read the contributor/maintainer guides but as this would be my
>> first package contribution, I may need some help using calm, etc.
>
> "cygport upload" takes care of this for you.
Thanks - was vaguely aware there were other commands, but obviously
never had use for them.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
next prev parent reply other threads:[~2017-04-26 2:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-25 22:42 Brian Inglis
2017-04-26 2:25 ` Yaakov Selkowitz
2017-04-26 2:59 ` Brian Inglis [this message]
2017-04-26 13:17 ` Jon Turney
2017-04-26 15:51 ` Brian Inglis
2017-04-26 18:30 ` Yaakov Selkowitz
2017-04-26 23:16 ` Brian Inglis
2017-04-26 23:20 ` Brian Inglis
2017-04-27 11:51 ` Jon Turney
2017-04-27 18:37 ` Brian Inglis
2017-04-27 23:31 ` Brian Inglis
2017-05-22 20:58 ` units issues Brian Inglis
2017-05-23 17:28 ` Achim Gratz
2017-05-23 21:49 ` Brian Inglis
2017-05-23 23:55 ` Doug Henderson
2017-05-24 2:37 ` Brian Inglis
2017-05-24 16:26 ` Buchbinder, Barry (NIH/NIAID) [E]
2017-05-24 17:34 ` Brian Inglis
2017-05-24 18:06 ` Achim Gratz
2017-05-24 18:13 ` Achim Gratz
2017-05-25 0:16 ` Brian Inglis
2017-05-25 2:07 ` Doug Henderson
2017-05-25 3:37 ` Brian Inglis
2017-04-27 17:28 ` [ITA] units Andrew Schulman
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=e65a0c0b-737e-2d10-b5c9-ef1ee5d6f99d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).