python3?

[MarkTr]

Is python3 support in the works? Is conary even used somewhere and in development?

[mibanescu]

Porting Conary to python3 is a huge undertaking. It has been discussed multiple times, here are some of the challenges:

• the recipe syntax is fairly python2 dependent. Changes in octal representations 0644 vs. 0o644 don't help much either. One would probably have to run a recipe conversion.
• the stream representation would probably have to be re-written - it is C code or cython currently, and I believe there were attempts for that before
• Conary has always been very Unicode-unfriendly, and python3's more strict separation of a string (unicode in py2) and byte array (strings in py2) is causing significant problems in porting to py3.
• not python 3 related, but relevant: a Conary package makes sense if the whole ecosystem is Conary (i.e. down to the operating system). Maintaining a Conary-based distribution (like Foresight) is a significant effort. Our attempt to use Conary as a wrapper around rpm packages is useful, but some of the advantages of Conary (finer-grain packages/components) are being lost. Unless one can fully automate the process of converting an established Linux distribution (Fedora, CentOS, etc) to Conary, the cost of maintaining the distro is too high.

Conary is still used internally, but is not under active development.

I would welcome any effort in moving Conary forward, of course :-)

[MarkTr]

recipe syntax isn't that big issue if you don't care of being compatible in that step.
I guess at the end rmake would need some deep changes too?

[mibanescu]

@protonesso - that's awesome. I won't be able to put any effort into it myself, unfortunately. But I would be interested in the outcome.

[Jheengut]

nice

…

On Fri, 21 Aug 2020 at 15:00, Ishimoto Shinobu ***@***.***> wrote: @mibanescu <https://github.com/mibanescu> @mtharp <https://github.com/mtharp> is there any reference documentation of conary? how the package format was made, how conary's database and system model work — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABGLYQLPCRDL5IHVGK7OMT3SBZHTZANCNFSM4DZR54FA> .