On 2019-02-13 23:26, Rainer Müller wrote:
> (...)
>
> This is a great initiative. One of our problems has always been that
> these tools kind of need to be written in the native language of the
> upstream package (Python, Perl, ...), because that is the only language
> with bindings to parse the p
Hey,
On 12.02.19 03:40, Cyril Roelandt wrote:
> I'm the author of upt.
Thanks for joining the discussion!
> On 2019-02-10 21:24, Mojca Miklavec wrote:
>> Hi,
>>
>> Last week I was sitting in cafeteria with the author of a new python
>> package "upt" (Universal packaging tool) whose aim is to pro
Dear Mojca,
My use case is far more ambitious. Thanks for the feedback though.
Kind regards.
Artur
From: Mojca Miklavec
Sent: 13 February 2019 09:38:35
To: Artur Szostak
Cc: Cyril Roelandt; MacPorts Development
Subject: Re: Universal packaging tool (for
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
. How does upt improve this
situation?
Best regards.
Artur
From: macports-dev on behalf of Cyril
Roelandt
Sent: 12 February 2019 03:40:50
To: Mojca Miklavec
Cc: MacPorts Development
Subject: Re: Universal packaging tool (for pypi, cpan, ruby, ...)
Hi
Hi!
I'm the author of upt.
On 2019-02-10 21:24, Mojca Miklavec wrote:
> Hi,
>
> Last week I was sitting in cafeteria with the author of a new python
> package "upt" (Universal packaging tool) whose aim is to provide
> automatic conversion from one of the repositories like pypi, cpan,
> ruby gems
Hi,
Last week I was sitting in cafeteria with the author of a new python
package "upt" (Universal packaging tool) whose aim is to provide
automatic conversion from one of the repositories like pypi, cpan,
ruby gems, npm, ... into any other package manager.
https://framagit.org/upt
https:/
