Why Do Software Packages Conflict?

Abstract : Inter-package conflicts require the presence of two or more packages in a particular configuration, and thus tend to be harder to detect and localize than conventional (intra- package) defects. Hundreds of such inter-package conflicts go undetected by the normal testing and distribution process until they are later reported by a user. The reason for this is that current meta-data is not fine-grained and accurate enough to cover all common types of conflicts. A case study of inter- package conflicts in Debian has shown that with more detailed package meta-data, at least one third of all package conflicts could be prevented relatively easily, while another one third could be found by targeted testing of packages that share common resources or characteristics. This paper reports the case study and proposes ideas to detect inter-package conflicts in the future.
Type de document :
Communication dans un congrès
9th Working Conference on Mining Software Repositories, Jun 2012, Zurich, Switzerland. 2012
Liste complète des métadonnées

https://hal.inria.fr/hal-00694022
Contributeur : Ralf Treinen <>
Soumis le : jeudi 3 mai 2012 - 13:40:01
Dernière modification le : jeudi 11 janvier 2018 - 06:17:49

Identifiants

  • HAL Id : hal-00694022, version 1

Collections

PPS | USPC

Citation

Cyrille Artho, Roberto Di Cosmo, Kuniyasu Suzaki, Ralf Treinen, Stefano Zacchiroli. Why Do Software Packages Conflict?. 9th Working Conference on Mining Software Repositories, Jun 2012, Zurich, Switzerland. 2012. 〈hal-00694022〉

Partager

Métriques

Consultations de la notice

46