From: Yasuhiro KIMURA <yasu@utahime.org>
To: cygwin@cygwin.com
Subject: Re: Update of packages by non-maintainer
Date: Thu, 21 May 2020 13:47:08 +0900 (JST) [thread overview]
Message-ID: <20200521.134708.978300984572490822.yasu@utahime.org> (raw)
In-Reply-To: <9098d0a3-a9ef-0c67-5e9f-af9bc5227bff@SystematicSw.ab.ca>
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
Subject: Re: Update of packages by non-maintainer
Date: Wed, 20 May 2020 08:32:59 -0600
> You should discuss changes and intent on cygwin list, post patches on
> cygwin-apps list.
Thank you for reply. My first candidate is anthy. Original anthy
projet has been inactive since 2009. But Debian forked it and made
improvement and enhancement. So I would like to switch codebase to
that of Debian. I just checked out cygwin anthy git repository and
started working but I have one question.
After project fork by Debian, release version scheme has changed.
While latest version from original project (and one used by cygwin
package) is "9100h", latest one from Debian is "0.4". That is, version
number decreses if I chage codebase to Debian. I know that some
packaging systems assume version number basically increases and that
decrement causes package upgrade failure. So I would like to know if
it also apply to Cygwin. And if it does then I also would like to know
how it should be handled.
Best Regards.
---
Yasuhiro KIMURA
next prev parent reply other threads:[~2020-05-21 4:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 10:18 Yasuhiro KIMURA
2020-05-20 11:09 ` marco atzeri
2020-05-20 14:32 ` Brian Inglis
2020-05-21 4:47 ` Yasuhiro KIMURA [this message]
2020-05-21 9:50 ` Andrey Repin
2020-05-21 10:16 ` Marco Atzeri
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=20200521.134708.978300984572490822.yasu@utahime.org \
--to=yasu@utahime.org \
--cc=cygwin@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).