Dear Artur, On Wed, 13 Feb 2019 at 09:18, Artur Szostak wrote: > > What is the current practical reality of tools like upt? i.e. how well do > they behave on real packages. For example, if I take all the .src.rpm > packages in say the Fedora repository, and attempt to convert them to > MacPorts packages, what percentage of the converted packages will actually > work out of the box? > I do not necessarily expect every package to work, some are too system > specific for that. However, my previous tinkering with such conversion tools > showed that the number is close to 0%. The problem was that they only really > work for simple packages with basically no dependencies. How does upt improve > this situation?
This is not the tool to convert Fedora packages to MacPorts packages, but to convert PyPi, CPAN, Ruby Gems, NPM, ... packages to *either* MacPorts or Fedora. I use cpan2port and pypi2port "all the time", or at least any time when I need to create a package from CPAN or PyPi. I would say that some 30% of the time these packages need some manual editing afterwards, but 100% of the time I get some useful starting point. The only thing I currently miss in UPT is some super easy way to update packages (which already went through some manual post-editing after the inital generation). In particular, I would want the tool to notify me about new or removed dependencies, for example, but other things as well. Mojca
