Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: yminsky@cs.cornell.edu
Cc: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>,
	zack@debian.org, caml-list@inria.fr,
	debian-ocaml-maint@lists.debian.org
Subject: Re: [Caml-list] binary compatibility of 3.08.3
Date: Sun, 16 Jan 2005 14:25:29 +0100	[thread overview]
Message-ID: <20050116132529.GA1467@pegasos> (raw)
In-Reply-To: <891bd33905011407017d58a116@mail.gmail.com>

On Fri, Jan 14, 2005 at 10:01:00AM -0500, Yaron Minsky wrote:
> It's worth mentioning that the pain of such upgrades is considerably
> reduced by the use of a package manager like GODI.  It's hardly
> perfect, but it makes such things much easier.

We already have a package manager, thank you all the same. The user won't see
a thing, but it is a hard thing for us debian package maintainers to rebuild
all packages that are dependent on ocaml on all 11 officially supported debian
architectures, and a bunch of unofficial ones, especially given the fact that
there are many dependencies, and there is at least one day lag in the
dependency chain building, and that some of our architectures are real slow to
build (m68k, mips/mipsel and s390 are the usual blockers, often arm and hppa
too). And so near to the sarge release, it is a real question if we should
forego the 3.08.3 changes or launch such a wide rebuild, which may miss the
freeze/release date anyway, or worse even, may make some important part of the
packages not being in the release at all. Luckily no ocaml package is part of
base/standard, and not affected by the base freeze.

Stuff like GODI are just hacky workaround for systems that lack real
system-wide package management and good ocaml integration like debian does :)

Friendly,

Sven Luther


  reply	other threads:[~2005-01-16 13:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-13  7:24 [Caml-list] Bug in Unix library on Mac? spiral voice
2005-01-13 16:53 ` Damien Doligez
2005-01-13 18:41   ` binary compatibility of 3.08.3 Stefano Zacchiroli
2005-01-13 23:02     ` [Caml-list] " Jacques Garrigue
2005-01-14 13:36       ` Sven Luther
2005-01-14 15:01         ` Yaron Minsky
2005-01-16 13:25           ` Sven Luther [this message]
2005-01-16 13:33             ` Berke Durak
2005-01-16 14:31               ` Sven Luther
2005-01-17  5:52             ` William Lovas
2005-01-15 12:07         ` Xavier Leroy
2005-01-16 13:37           ` Sven Luther
2005-01-16 16:26             ` Jacques Garrigue
2005-01-16 18:23               ` Sven Luther
2005-01-20  5:53                 ` Jacques Garrigue
2005-01-20  8:59                   ` Sven Luther
2005-01-16 21:08             ` Damien Doligez
2005-01-16 22:27               ` Sven Luther
2005-01-14 15:25       ` Marcin 'Qrczak' Kowalczyk
2005-01-27 15:40       ` Christophe TROESTLER
2005-01-30  6:11         ` Sven Luther
2005-01-30 11:12           ` Christophe TROESTLER
2005-01-30 15:28           ` Stefan Monnier
2005-01-31  7:09             ` Sven Luther

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=20050116132529.GA1467@pegasos \
    --to=sven.luther@wanadoo.fr \
    --cc=caml-list@inria.fr \
    --cc=debian-ocaml-maint@lists.debian.org \
    --cc=garrigue@math.nagoya-u.ac.jp \
    --cc=yminsky@cs.cornell.edu \
    --cc=zack@debian.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