Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support for binary packages #1159

Open
UnixJunkie opened this issue Feb 4, 2014 · 5 comments
Open

support for binary packages #1159

UnixJunkie opened this issue Feb 4, 2014 · 5 comments

Comments

@UnixJunkie
Copy link
Contributor

people using embedded systems tell me they'd like OPAM to be able to install
pre-compiled versions of packages.

I'd also like this feature but for a different reason: as a sysadmin
I like software to install fast and possibly on many hosts at the same time.

@rdicosmo
Copy link
Contributor

rdicosmo commented Feb 4, 2014

Indeed, binary packages are quite useful for many people, but
source and binary packages are a completely different business,
and require different metadata, in particular for OCaml binaries.

Before embarking into an implementation of binary packages in
opam, I strongly recommend to read thoroughly at least this
paper

@Article{DBLP:journals/siu/DogguyGGZ11,
author = {Mehdi Dogguy and
St{'e}phane Glondu and
Sylvain Le Gall and
Stefano Zacchiroli},
title = {Enforcing Type-Safe Linking using Inter-Package Relationships},
journal = {Stud. Inform. Univ.},
volume = {9},
number = {1},
year = {2011},
pages = {129-157},
ee = {http://studia.complexica.net/index.php?option=com_content{\&}view=article{\&}id=188\%3Aenforcing-type-safe-linking-using-inter-package-relationships-pp-129-157},
bibsource = {DBLP, http://dblp.uni-trier.de}
}

and ideally, to come and spend time discussing all these issues
face to face with the OCaml Debian team.

On Mon, Feb 03, 2014 at 05:02:38PM -0800, Francois Berenger wrote:

people using embedded systems tell me they'd like OPAM to be able to install
pre-compiled versions of packages.

I'd also like this feature but for a different reason: as a sysadmin
I like software to install fast and possibly on many hosts at the same time.


Reply to this email directly or view it on GitHub.*

Roberto Di Cosmo


Professeur En delegation a l'INRIA
PPS E-mail: roberto@dicosmo.org
Universite Paris Diderot WWW : http://www.dicosmo.org
Case 7014 Tel : ++33-(0)1-57 27 92 20
5, Rue Thomas Mann
F-75205 Paris Cedex 13 Identica: http://identi.ca/rdicosmo

FRANCE. Twitter: http://twitter.com/rdicosmo

Attachments:
MIME accepted, Word deprecated

http://www.gnu.org/philosophy/no-word-attachments.html

Office location:

Bureau 3020 (3rd floor)
Batiment Sophie Germain
Avenue de France

Metro Bibliotheque Francois Mitterrand, ligne 14/RER C

GPG fingerprint 2931 20CE 3A5A 5390 98EC 8BFC FCCA C3BE 39CB 12D3

@mww42
Copy link

mww42 commented Feb 4, 2014

I am one of the embedded systems guys; compiling on my low-end ARM system is not much fun -- especially large projects like OCaml itself.
I don't see how the problem described in the article only holds for binary packages and not source-based ones: If you introduce an incompatibility (e.g. duplicate symbol) you only realize that when you re-compile all the dependents. A straight-forward solution to this would be to always increase the revision/minor version of all dependent packages on an update; if I'm not mistaken, opam already does that implicitly on the local installation.

@AltGr AltGr modified the milestone: outgoing Feb 10, 2014
@AltGr
Copy link
Member

AltGr commented Feb 10, 2014

This is a long-standing feature wish that we have plans for, see https://github.com/ocaml/opam/wiki/Roadmap

@UnixJunkie
Copy link
Contributor Author

This is linked to #629

@AltGr AltGr added this to the Next milestone Jul 4, 2014
@AltGr
Copy link
Member

AltGr commented Jun 1, 2016

We now have tracking of installed files, so this could be used to extract binary packages (at least for packages that only do additions, which should be almost all of them)

@rjbou rjbou removed this from the Next milestone May 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants