[Scons-dev] RPM helper functions, where should they go?

[Kenny, Jason L]

Is there any relationship with the RPM functions in tools/packaging/rpm.py??

Personally I like the idea of an independent RPM tool from the packaging logic.

Jason


-----Original Message-----
From: scons-dev-bounces at scons.org [mailto:scons-dev-bounces at scons.org] On Behalf Of Dirk Bächle
Sent: Tuesday, September 25, 2012 12:39 PM
To: SCons developer list
Subject: [Scons-dev] RPM helper functions, where should they go?

Hi there,

for fixing the current Buildbot failures I still have to fight down several RPM tests. They check the names of the created RPM files, which differ depending on the used hardware/os combination.
I'd like to wrap the original RPM functions for canonicalizing machine/system names and all the supporting stuff to a Python module, but I can't make up my mind about where the file should go.
It should be possible to import it from the RPM/packaging stuff and the test suite in QMTest as well.

My suggestion would be a new file "rpmrc.py" in the SCons/Tools dir, alongside the "rpm.py" tool.
Does this make sense or do we have a better place?

Best regards,

Dirk

P.S.: For cases like this it would be cool to have a "scons-common" 
package with stuff that can get used by SCons itself, the test framework and perhaps even Parts. It could offer basic things like "starting processes, is-this-a-list?" and similar stuff, which are partly spread over the whole codebase in different variations...

_______________________________________________
Scons-dev mailing list
Scons-dev at scons.org
http://two.pairlist.net/mailman/listinfo/scons-dev