odcs

#30 Split odcs into separate parts
Closed Opened by cqi.

Closed
Reopen Issue

As we discussed in IRC, it would be great to split odcs to separate parts in order to reuse part of the code and delivery conveniently. The idea is odcs will have three parts,

  • client, the client API used by any other application to interact with ODCS server.
  • odcs, the ODCS server.
  • common, the shared library used by both client and server.

While trying to make subpackage odcs-client, I found odcs/__init__.py is not usable as it contains lots of code that is not relative. This issue should be helpful.

Done already.

Metadata Update from @jkaluza:
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/pungi/odcs/issues/30

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.