Path: csiph.com!newsfeed.xs4all.nl!newsfeed9.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Andrius Merkys Newsgroups: linux.debian.maint.java Subject: Re: packaging Go runtime for ANTLR4 Date: Thu, 29 Jul 2021 09:10:02 +0200 Message-ID: References: X-Original-To: debian-java@lists.debian.org X-Mailbox-Line: From debian-java-request@lists.debian.org Thu Jul 29 07:09:38 2021 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.503 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, NICE_REPLY_A=-0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001] autolearn=ham autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .gmail. - helo: .mail-lj1-f177.google. - helo-domain: .google.) FROM/MX_MATCHES_HELO(DOMAIN)=-2; rate: -5.5 X-Gm-Message-State: AOAM533kJvOaBSLwrk4abtRHMPi4s93sVMtMfigx0G2joFoF0D8HEm5s 7SNj1+mCAI2uPRsIqWkXOVaoyRkD1OY= X-Google-SMTP-Source: ABdhPJx4tzrd06VVbAKyKSgkfv0IwPFOfRnrZpgIQj6XIMLyE2G1XGOOsvVLD8FcyRIpjJiaEqVkGA== X-Received: by 2002:a2e:9843:: with SMTP id e3mr1969962ljj.498.1627542565180; Thu, 29 Jul 2021 00:09:25 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/22894 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/f144783d-8fe3-bbc2-426f-5c19a67ffdb5@debian.org Approved: robomod@news.nic.it Lines: 16 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 29 Jul 2021 10:09:23 +0300 X-Original-Message-ID: X-Original-References: Xref: csiph.com linux.debian.maint.java:12265 Hello, Maintainer of antlr4-cpp-runtime here. On 2021-07-28 22:36, Nilesh Patra wrote: > 2) Do "$something-else" for all these packages to stay in sync - again, > probably bumping versions only when needed. > With this approach, I do not see a problem in introducing a Go runtime > source package there I was not aware of out-of-sync problem, thanks for pointing it out. Maybe an antlr4 packaging team could be set up to coordinate synchronized version bumps? Best, Andrius