From: Andrey Repin <anrdaemon@yandex.ru>
To: Yasuhiro KIMURA <yasu@utahime.org>, cygwin@cygwin.com
Subject: Re: Update of packages by non-maintainer
Date: Thu, 21 May 2020 12:50:27 +0300 [thread overview]
Message-ID: <1886504821.20200521125027@yandex.ru> (raw)
In-Reply-To: <20200521.134708.978300984572490822.yasu@utahime.org>
Greetings, Yasuhiro KIMURA!
>> 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.
It does. This is why you would see test and pre-release versions posted as
X.Y-0.Z and release versions posted as X.Y-Z.
> And if it does then I also would like to know how it should be handled.
An interesting question, given nonstandard original versioning.
--
With best regards,
Andrey Repin
Thursday, May 21, 2020 12:46:55
Sorry for my terrible english...
next prev parent reply other threads:[~2020-05-21 10:05 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
2020-05-21 9:50 ` Andrey Repin [this message]
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=1886504821.20200521125027@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=yasu@utahime.org \
/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).