[opam-devel] ows reports

Thomas Gazagnaire thomas at gazagnaire.org
Sun Sep 28 02:29:15 BST 2014


> Let me rephrase then. I think in some cases the ocaml version as an architecture. For an user point-of-view (and a maintainer) I am interested by two different questions:

sorry, forgot to write some words ... I meant:

 "I think in some cases the ocaml version should not be considered as an architecture"


> 
> 1. Can I install the given package for at least one version of the compiler (in this case: the compiler is a normal package that you can upgrade/downgrade, not an architecture which doesn't change). if not, is it because:
>   a) the package is in "broken" (there is a strong conflict in its dependencies)
>   b) the package depends on a "broken" package
> 
> 2. Can I install the given package with the given compiler version: if not, is it because:
>   a) the package is "unavailable" for the given compiler (because 'available' field evaluate to false) or
>   b) the package depends on an "unavailable" package
> 
> http://ows.irill.org/table.html show an empty square for 2.a but seems to conflats 1.a, 1.b and 2.b. I think that would be very helpful to highlight 1.a (1.b and 2.b could also be useful to know the root causes of the problems, ie. either fix 1.a or port 2.a to the given ocaml version).
> 
> Best,
> Thomas
> 
> 
>> 
>> in the previous message
>> 
>> 2014-09-27 20:14 GMT+02:00 Roberto Di Cosmo <roberto at dicosmo.org>:
>> Dear Thomas,
>>    I have some difficulty in understanding what exactly you do not understand in the reports present on OWS.
>> 
>> Let me try to provide a few hints; a package is reported as "bad" for a given version and a given architecture if there is no way to satisfy its dependencies.
>> 
>> This means that there is no way you can install it using opam, and even if the "code" shipped with the package may be perfectly fine, the "package" itself is nevertheless useless.
>> 
>> This is why it is often termed "broken", following a terminology that is now standard in the world of package based distribution, as it has been in use for a couple of decades.
>> 
>> Why a package is broken, who is responsible of fixing it, is another story: it can be the package maintainer that did not update the dependencies, or the maintainer of a dependency that has wrongly removed it, or the release manager that has not spotted the problem.
>> 
>> In the framework of the Mancoosi project we have developed a full suite of tools to help improving the quality of a package based system, and it so happen that all these tools are even written in OCaml.
>> 
>> I really do suggest that people on this list take the time and read the short support material that was developed by Zack, Ralf and me for the HATS summer school, and that is available here: 
>> http://www.dicosmo.org/Publications/Hats2012.html
>> 
>> All the best
>> 
>> --
>> Roberto
>> 
>> 
>> 2014-09-27 19:43 GMT+02:00 Thomas Gazagnaire <thomas at gazagnaire.org>:
>> Hi,
>> 
>> I had a quick look at "opam weather services" reports and I am a bit puzzled at how the statistic are computed. It seems that a package is considered as "broken" when one of its dependency cannot be installed. I'm not sure it makes sense: in the case the dependency is not available on a given platform / compiler version, then all the packages which depend upon it are not available as well as "availability" is a transitive relation in opam. These packages are not "broken".
>> 
>> Especially, on that page: http://ows.irill.org/table.html a lot of "bad" result are in fact simply a result the package not available for the given compiler version.
>> 
>> I'm sure they are packages which are actually broken (ie. there are no version of ocaml where they can be installed) and these should be much more useful to high-light in order than someone try to fix the descriptions (for instance me, when I am bored and have nothing else to do).
>> 
>> Best,
>> Thomas
>> _______________________________________________
>> opam-devel mailing list
>> opam-devel at lists.ocaml.org
>> http://lists.ocaml.org/listinfo/opam-devel
>> 
>> 
>> 
>> -- 
>> Roberto Di Cosmo
>>  
>> ------------------------------------------------------------------
>> Professeur               En delegation a l'INRIA
>> PPS                      E-mail: roberto at 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 320 (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 
>> 
>> 
>> 
>> -- 
>> Roberto Di Cosmo
>>  
>> ------------------------------------------------------------------
>> Professeur               En delegation a l'INRIA
>> PPS                      E-mail: roberto at 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 320 (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 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ocaml.org/pipermail/opam-devel/attachments/20140928/f5c4ab4b/attachment-0001.html>


More information about the opam-devel mailing list