[opensuse-packaging] Proper dev project for a small collection of C utility libs with python bindings
All, I'm about to submit 6 new small packages: libevt, libevtx, libregf, libmsiecf, liblnk, libvshadow. My basic question is what devel project I should send these to and if I should leave them as 6 discrete projects, or maybe try to combine them somehow. I've thought about just pushing all 6 to devel:libraries If that is a good choice let me know. == details All of them are from the same upstream author and have the same structure, all hosted at the same place etc. The specfiles are all very similar. For each one there is a c library created, a python bindings sub-package and a end-user tools sub-package (eg. evttools, etc.) with a couple simple tools each. My use case is a security tool that uses the python bindings of all 6, so in theory I could put them there, but it seems like the wrong place to me, but the "tools" sub-projects would all actually qualify as security tools for a forensic examiner. (I already have 15 or 20 forensic tools in the security project, so maybe it is time for me to create a security:dfir sub-project and just put everything in there?) Thanks Greg -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
On Fri, Mar 29, 2013 at 12:45:24PM -0400, Greg Freemyer wrote:
All,
I'm about to submit 6 new small packages: libevt, libevtx, libregf, libmsiecf, liblnk, libvshadow.
My basic question is what devel project I should send these to and if I should leave them as 6 discrete projects, or maybe try to combine them somehow.
I've thought about just pushing all 6 to devel:libraries If that is a good choice let me know.
== details
All of them are from the same upstream author and have the same structure, all hosted at the same place etc.
The specfiles are all very similar. For each one there is a c library created, a python bindings sub-package and a end-user tools sub-package (eg. evttools, etc.) with a couple simple tools each.
My use case is a security tool that uses the python bindings of all 6, so in theory I could put them there, but it seems like the wrong place to me, but the "tools" sub-projects would all actually qualify as security tools for a forensic examiner. (I already have 15 or 20 forensic tools in the security project, so maybe it is time for me to create a security:dfir sub-project and just put everything in there?)
I would not create an another sub-devel-project if there are not stronger reason that I have no idea where to put my package. Please note that devel projects does not make any sense for most of of packages we have in openSUSE, therefor feel free to submit them into security, or utilities or devel:openSUSE:Factory, or whatever reasonable existing project you will find. Regards Michal Vyskocil
* Greg Freemyer (greg.freemyer@gmail.com) [20130329 17:47]:
My basic question is what devel project I should send these to and if I should leave them as 6 discrete projects, or maybe try to combine them somehow.
I'd make leave them distinct packages as that eases maintenance in the long run.
I've thought about just pushing all 6 to devel:libraries If that is a good choice let me know.
devel:libraries:c_c++ would IMO be the right place for these. hth Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Philipp Thomas <pth@suse.de> wrote:
* Greg Freemyer (greg.freemyer@gmail.com) [20130329 17:47]:
My basic question is what devel project I should send these to and if I should leave them as 6 discrete projects, or maybe try to combine them somehow.
I'd make leave them distinct packages as that eases maintenance in the long run.
I've thought about just pushing all 6 to devel:libraries If that is a good choice let me know.
devel:libraries:c_c++ would IMO be the right place for these.
hth Philipp
I'll do that. In this case, they are all "required" at run time, but not "buildrequired" so that simplifies things. If they were buildrequired for a security tool, would I just linkpak them from utilities to security? (I'm a security repo maintainer because of the security tools I have in there.) Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
Hi Greg, * Greg Freemyer (greg.freemyer@gmail.com) [20130403 15:09]:
If they were buildrequired for a security tool, would I just linkpak them from utilities to security? (I'm a security repo maintainer because of the security tools I have in there.)
Yes, if you don't plan to have the libraries and possibly tools in factory also you'd need to either linkpac the libraries or build against the library repo, i.e. select it instead of plain factory. hth Philipp -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org
participants (3)
-
Greg Freemyer
-
Michal Vyskocil
-
Philipp Thomas