The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. ex. Some numerals are expressed as "XNUMX".
Copyrights notice
The original paper is in English. Non-English content has been machine-translated and may contain typographical errors or mistranslations. Copyrights notice
O gerenciador de pacotes (PM) é crucial para a maioria das pilhas de tecnologia, atuando como um intermediário para garantir que um pacote de dependência verificado seja corretamente instalado, configurado ou removido de um aplicativo. A diversidade nas pilhas de tecnologia levou a dezenas de PMs com vários recursos. Embora nosso estudo recente indique que os recursos de gerenciamento de pacotes do PM estão relacionados às experiências do usuário final, não está claro quais são esses problemas e quais informações são necessárias para resolvê-los. Neste artigo, investigamos os problemas de PM enfrentados pelos usuários finais por meio de um estudo empírico de conteúdo no Stack Overflow (SO). Realizamos uma análise qualitativa de 1,131 perguntas e suas postagens de respostas aceitas para três PMs populares (ou seja, Maven, npm e NuGet) para identificar tipos de problemas, causas subjacentes e suas resoluções. Nossos resultados confirmam que os usuários finais têm dificuldades com o uso de ferramentas de PM (aproximadamente 64-72%). Observamos que a maioria dos problemas são levantados pelos usuários finais devido à falta de instruções e mensagens de erros das ferramentas PM. Em termos de resolução de problemas, descobrimos que o compartilhamento de links externos é a prática mais comum para resolver problemas de PM. Além disso, observamos que links que apontam para recursos úteis (ou seja, sites de documentação oficial, tutoriais, etc.) são compartilhados com mais frequência, indicando o potencial de suporte de ferramentas e a capacidade de fornecer informações relevantes para usuários finais de PM.
Syful ISLAM
Noakhali Science and Technology University
Raula GAIKOVINA KULA
Nara Institute of Science and Technology
Christoph TREUDE
University of Melbourne
Bodin CHINTHANET
Nara Institute of Science and Technology
Takashi ISHIO
Nara Institute of Science and Technology
Kenichi MATSUMOTO
Nara Institute of Science and Technology
The copyright of the original papers published on this site belongs to IEICE. Unauthorized use of the original or translated papers is prohibited. See IEICE Provisions on Copyright for details.
Copiar
Syful ISLAM, Raula GAIKOVINA KULA, Christoph TREUDE, Bodin CHINTHANET, Takashi ISHIO, Kenichi MATSUMOTO, "An Empirical Study of Package Management Issues via Stack Overflow" in IEICE TRANSACTIONS on Information,
vol. E106-D, no. 2, pp. 138-147, February 2023, doi: 10.1587/transinf.2022MPP0001.
Abstract: The package manager (PM) is crucial to most technology stacks, acting as a broker to ensure that a verified dependency package is correctly installed, configured, or removed from an application. Diversity in technology stacks has led to dozens of PMs with various features. While our recent study indicates that package management features of PM are related to end-user experiences, it is unclear what those issues are and what information is required to resolve them. In this paper, we have investigated PM issues faced by end-users through an empirical study of content on Stack Overflow (SO). We carried out a qualitative analysis of 1,131 questions and their accepted answer posts for three popular PMs (i.e., Maven, npm, and NuGet) to identify issue types, underlying causes, and their resolutions. Our results confirm that end-users struggle with PM tool usage (approximately 64-72%). We observe that most issues are raised by end-users due to lack of instructions and errors messages from PM tools. In terms of issue resolution, we find that external link sharing is the most common practice to resolve PM issues. Additionally, we observe that links pointing to useful resources (i.e., official documentation websites, tutorials, etc.) are most frequently shared, indicating the potential for tool support and the ability to provide relevant information for PM end-users.
URL: https://global.ieice.org/en_transactions/information/10.1587/transinf.2022MPP0001/_p
Copiar
@ARTICLE{e106-d_2_138,
author={Syful ISLAM, Raula GAIKOVINA KULA, Christoph TREUDE, Bodin CHINTHANET, Takashi ISHIO, Kenichi MATSUMOTO, },
journal={IEICE TRANSACTIONS on Information},
title={An Empirical Study of Package Management Issues via Stack Overflow},
year={2023},
volume={E106-D},
number={2},
pages={138-147},
abstract={The package manager (PM) is crucial to most technology stacks, acting as a broker to ensure that a verified dependency package is correctly installed, configured, or removed from an application. Diversity in technology stacks has led to dozens of PMs with various features. While our recent study indicates that package management features of PM are related to end-user experiences, it is unclear what those issues are and what information is required to resolve them. In this paper, we have investigated PM issues faced by end-users through an empirical study of content on Stack Overflow (SO). We carried out a qualitative analysis of 1,131 questions and their accepted answer posts for three popular PMs (i.e., Maven, npm, and NuGet) to identify issue types, underlying causes, and their resolutions. Our results confirm that end-users struggle with PM tool usage (approximately 64-72%). We observe that most issues are raised by end-users due to lack of instructions and errors messages from PM tools. In terms of issue resolution, we find that external link sharing is the most common practice to resolve PM issues. Additionally, we observe that links pointing to useful resources (i.e., official documentation websites, tutorials, etc.) are most frequently shared, indicating the potential for tool support and the ability to provide relevant information for PM end-users.},
keywords={},
doi={10.1587/transinf.2022MPP0001},
ISSN={1745-1361},
month={February},}
Copiar
TY - JOUR
TI - An Empirical Study of Package Management Issues via Stack Overflow
T2 - IEICE TRANSACTIONS on Information
SP - 138
EP - 147
AU - Syful ISLAM
AU - Raula GAIKOVINA KULA
AU - Christoph TREUDE
AU - Bodin CHINTHANET
AU - Takashi ISHIO
AU - Kenichi MATSUMOTO
PY - 2023
DO - 10.1587/transinf.2022MPP0001
JO - IEICE TRANSACTIONS on Information
SN - 1745-1361
VL - E106-D
IS - 2
JA - IEICE TRANSACTIONS on Information
Y1 - February 2023
AB - The package manager (PM) is crucial to most technology stacks, acting as a broker to ensure that a verified dependency package is correctly installed, configured, or removed from an application. Diversity in technology stacks has led to dozens of PMs with various features. While our recent study indicates that package management features of PM are related to end-user experiences, it is unclear what those issues are and what information is required to resolve them. In this paper, we have investigated PM issues faced by end-users through an empirical study of content on Stack Overflow (SO). We carried out a qualitative analysis of 1,131 questions and their accepted answer posts for three popular PMs (i.e., Maven, npm, and NuGet) to identify issue types, underlying causes, and their resolutions. Our results confirm that end-users struggle with PM tool usage (approximately 64-72%). We observe that most issues are raised by end-users due to lack of instructions and errors messages from PM tools. In terms of issue resolution, we find that external link sharing is the most common practice to resolve PM issues. Additionally, we observe that links pointing to useful resources (i.e., official documentation websites, tutorials, etc.) are most frequently shared, indicating the potential for tool support and the ability to provide relevant information for PM end-users.
ER -