From: Gabriel Kerneis <kerneis@pps.jussieu.fr>
To: Jon Ludlam <jonathan.ludlam@eu.citrix.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] opam and versions
Date: Mon, 22 Oct 2012 15:58:28 +0100 [thread overview]
Message-ID: <20121022145827.GA10467@kerneis.info> (raw)
In-Reply-To: <50854D34.4000301@eu.citrix.com>
On Mon, Oct 22, 2012 at 02:42:12PM +0100, Jon Ludlam wrote:
> If someone really wants to release a stable version of their thing and it's
> dependent upon an upstream project with only a github repo, should the
> developer engage the upstream devs and request at least a tag, or should they
> make their own tarball/github fork?
If you have developed and tested your build with some specific upstream
snapshot, but prefer not to embed it, you do not even need a tag: you can depend
directly on the relevant upstream commit. If opam does not support this, it
should definitely be added since it solves the "unresponsive upstream" issue.
Whether it is a good idea to depend on unstable version (and carve this
dependency in stone!) is another issue…
Best,
--
Gabriel
next prev parent reply other threads:[~2012-10-22 14:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-22 13:42 Jon Ludlam
2012-10-22 14:58 ` Gabriel Kerneis [this message]
2012-10-22 15:16 ` Anil Madhavapeddy
2012-10-28 11:32 ` Thomas Gazagnaire
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=20121022145827.GA10467@kerneis.info \
--to=kerneis@pps.jussieu.fr \
--cc=caml-list@inria.fr \
--cc=jonathan.ludlam@eu.citrix.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 NNTP newsgroup(s).