On 28/08/13 17:07 -0400, Matthew Miller wrote:
On Wed, Aug 28, 2013 at 03:27:34PM -0400, Vincent Batts wrote:For a recent tool, I packaged up a single library, that could be a current example of getting libraries packaged, but not where I want to get to.So, is that example what we should follow if we have some libraries we'd like to package up now? (Should these basically only generate -devel subpackages?) Is it okay to review it copying your basic idea now but with the caveat that we'll update if we get closer to what you want to get to?
golang libraries are basically -devel packages, not just subpackages. The part that is going to need revision is how to handle that fact that any given library, should provide subpackages for all the arch's of *.a, that can be installed individually or exist together. Further, I have tasks to work putting the packaging guideline documentation on the fedora site. The Flock workshop was good, though was mostly abstract discussion, not substantive work on the documentation. as for examples: * import "launchpad.net/goyaml" - https://brewweb.devel.redhat.com/packageinfo?packageID=43627* go-cdnauth an internal tool, that has imports as well - https://brewweb.devel.redhat.com/packageinfo?packageID=43625
Take care, vb
Attachment:
pgpyK7371xOHG.pgp
Description: PGP signature
-- packaging mailing list packaging@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/packaging
