On Mon, Feb 6, 2012 at 8:26 PM, Greg Freemyer wrote:

Further, this is an application, not a library, but since its written python, should it be python-distorm?

If it's an application, it shouldn't have the python- prefix. About the 3... is there a distorm2? -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Tue, 7 Feb 2012 00:26, Greg Freemyer wrote:

All,

I want to package distorm (distorm3) from http://code.google.com/p/distorm/

The name is distorm, but the source is distributed is distorm3-1.0.zip

And the zip file expands to distorm3-1.0.

I've got a very preliminary specfile at:

https://build.opensuse.org/package/files?package=distorm&project=home%3Agregfreemyer%3ATools-for-forensic-boot-cd

Since '-' is illegal in the version number, it seems easiest to package this as distorm3.

Further, this is an application, not a library, but since its written python, should it be python-distorm?

Ok, distorm stands for "diStorm3 binary stream disassembler library", so "distorm3" is a good and valid choice for a name, esp. in view of future releases. Now the python- prefix is an other matter. (I think there was a discussion on this list about, but please correct me if I'm wrong here.) - Unconditional yes for pure libraries. - Can but not must for mixed packages (lib + app). - Can but not needed for apps. Personally, I think adding the prefix takes notthing away, but gives a clear hint of "Needs python to work". Just my 2 ct, and why. - Yamaban. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On Mon, Feb 6, 2012 at 9:44 PM, Yamaban wrote:

Ok, distorm stands for "diStorm3 binary stream disassembler library", so "distorm3" is a good and valid choice for a name, esp. in view of future releases.

Now the python- prefix is an other matter. (I think there was a discussion on this list about, but please correct me if I'm wrong here.)

- Unconditional yes for pure libraries. - Can but not must for mixed packages (lib + app). - Can but not needed for apps.

My rule of thumb. Do I use kaffeine or C++-kaffeine? Do I use powertop or python-powertop? With apps, the language used to build the apps is irrelevant as the examples illustrate. -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org