<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi,<div><br><div><div>Le 1 févr. 2014 à 15:30, Anil Madhavapeddy <<a href="mailto:anil@recoil.org">anil@recoil.org</a>> a écrit :</div><br><blockquote type="cite">My point is that the user originally obtains their version of OPAM via their<br>OS package manager (Homebrew, apt, BSD ports, Yum, etc). All of these managers<br>provide a mechanism to warn the user of any upgrade steps that need to happen<br>when upgrading their distribution, and so is an ideal way to update OPAM<br>itself in the event of incompatible future changes.<br><br>In contrast, `opam update` is part of a *development* workflow, not a system<br>upgrade path. I do that when I want to recompile some part of my working<br>trees to a new package set, and often follow it up with an upgrade (via -u).<br></blockquote><div><br></div><div>Sorry, but I disagree here. I'm a regular user of tlmgr the package manager of tex-live and I appreciate the fact that it informs me of upgrade of itself and allows me to upgrade itself. (I'm not plainly satisfied that it forces me to do so...)</div><div><br></div><div>We are, more and more, evolving in a jungle of package managers (all using specific workflows for good reasons), I dream that one day, we will be able to simplify this landscape...</div><div><br></div><div>Personally, I use the os x system for updates + homebrew + tlmgr + opam + cabal + cpan + rubyGems + easy_install or pip + firefox update system + emacs package system + eclipse + maven... Hard to even build the list of all the package manager one's use...</div><div><br></div>Fabien<br></div><br><div>
<table style="background-color:#f1f1f1; border:1px #ddd solid;">
<tbody><tr>
<td>
<a href="http://www.telecom-bretagne.eu" target="_blank"><img src="https://img.mines-telecom.fr/signature-mail/logos/logo-tb.png" title="Site web Télécom Bretagne" alt="Télécom Bretagne" style="padding:4px 0 4px 4px;"></a>
</td>
<td>
<div style="float:left; font: 13px/1.5 sans-serif; color:#555; padding:8px 15px;">
<strong>Fabien DAGNAT</strong><br>
Maître de conférences au département informatique<br>
Responsable de la filière Systèmes Logiciels et Réseaux<br>
Tél. : (0 | 33) 2 29 00 14 09
</div>
<div style="float:left; font: bold 11px/1.5 sans-serif; color:#888; padding:8px 15px;">
Technopôle Brest-Iroise,
CS 83818<br>
29238 Brest Cedex 3, France <br>
<a href="http://www.telecom-bretagne.eu" target="_blank" style="text-decoration:none;"><img src="http://img.mines-telecom.fr/signature-mail/social/web.png" title="Site web Télécom Bretagne" alt="Site web Télécom Bretagne" style="padding:3px 10px 4px 0;"></a><a href="http://www.telecom-bretagne.eu/lexians/" target="_blank" style="text-decoration:none;"><img src="http://img.mines-telecom.fr/signature-mail/social/blog.png" title="Blog Télécom Bretagne" alt="Blog Télécom Bretagne" style="padding:3px 10px 4px 0;"></a><br>
Une école de <a href="http://www.mines-telecom.fr" target="_blank">l'Institut Mines-Télécom</a>
</div>
</td>
</tr>
</tbody></table>
</div>
<br></div></body></html>