From: Eugen Stan <eugen.stan@netdava.com>
To: 67328@debbugs.gnu.org
Subject: [bug#67328] [PATCH] Upgrade clojure-tools to 1.11.1.1413 + clojure-tools-deps transition
Date: Fri, 24 Nov 2023 07:27:34 +0200 [thread overview]
Message-ID: <2be45960-15b1-45dc-a1f2-bc17b600b3f5@netdava.com> (raw)
In-Reply-To: <20231120200909.126545-1-eugen.stan@netdava.com>
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
Hello Christopher,
Thank you for taking a look at this.
I meant downstream, thanks.
IMO there might be libs that use the alpha version/
Removing clojure-tools-deps-alpha means those packages will have to find
another way around this.
I would put a deprecation notice and remove it at a later time.
Both packages can co-exist (probably in the same app) - they use
different namespaces (a lot of Clojure projects do not use 'semantic'
versioning)
I can split the commit in 2 or 3 parts:
- one adds clojure-tools-deps
- one makes the switch
- optional one drops clojure-tools-deps-alpha
This seems like busy-work, but I think I get the point.
Will close this and send the other + link them to this issue.
Regards,
--
Eugen Stan
[-- Attachment #2: eugen_stan.vcf --]
[-- Type: text/vcard, Size: 181 bytes --]
begin:vcard
fn:Eugen Stan
n:Stan;Eugen
email;internet:eugen.stan@netdava.com
tel;cell:+40720898747
x-mozilla-html:FALSE
url:https://www.netdava.com
version:2.1
end:vcard
next prev parent reply other threads:[~2023-11-24 5:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-20 20:09 [bug#67328] [PATCH] Upgrade clojure-tools to 1.11.1.1413 + clojure-tools-deps transition eugen.stan
2023-11-23 10:22 ` [bug#67328] QA review for 67328 Eugen Stan
2023-11-23 13:51 ` Christopher Baines
2023-11-23 13:52 ` [bug#67328] [PATCH] Upgrade clojure-tools to 1.11.1.1413 + clojure-tools-deps transition Christopher Baines
2023-11-24 5:56 ` Eugen Stan
2023-11-24 5:27 ` Eugen Stan [this message]
2024-02-06 11:55 ` bug#67328: Close as duplicate Andreas Enge
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=2be45960-15b1-45dc-a1f2-bc17b600b3f5@netdava.com \
--to=eugen.stan@netdava.com \
--cc=67328@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.