-
Notifications
You must be signed in to change notification settings - Fork 26
Structure of RPM package #68
Comments
Before we finalize the RPM for The issues I'm referring to are: |
What is the usage of these:
By which I mean
|
Replying to @bdorney's comment, those bugs are not connected to this development. |
Same question here as in In the RPM structure above how are you handling: Here |
The following should be in the
The following files have pieces that are imported by other tools:
Yes as shown above. |
Let me clarify a bit:
Probably a request for a future improvement, but to properly package this as a python package, the separation between modules and scripts/executables should be exact, i.e., nothing that gets See response in cms-gem-daq-project/vfatqc-python-scripts#160 for more info on handling the |
The following files:
Based on this what I understand as your request is that the executable scripts only include a:
And do not include additional function definitions. For example in
You would prefer these functions be in a utilities or other file and imported here? Do I understand the request correctly: Executables include only a |
Okay we'll move that discussion to that issue in |
As a bare minimum, no additional function definitions that are used elsewhere, as it complicates the package organization. |
Okay. So we will try to resolve this nested mishmash and try to segment things into two subdirectories: https://github.com/cms-gem-daq-project/gem-plotting-tools/tree/master/macros e.g. the other scripts like Would you like this addressed as a hotfix to |
Hmm, I guess in this case the distinction I'm trying to raise is quite muddled... Effectively what I want is to separate the "library" from the "things that use the library" So probably in the short term, I'll put a select set of tools in |
…import mismash discussed in cms-gem-daq-project#68
I think it's safe to close this issue. Reopen if still relevant. |
Information
PYTHONPATH
, e.g., (defaultpython
oncc7):
/usr/lib/python2.7/site-packages/`gempython
, under which there would be thegemplotting
,vftaqc
, etc., modules, but this is still to be finalized into a proposal, and then discussedimport
statements, but I have for the most part decided on a workable solution for people who are doing private development and not using the production softwareamc_info_uhal.py
will all go into/opt/cmsgemos/bin
, to make it simple to add this to thePATH
variable and have the script readyCurrent RPM structure (UPDATED 12-03-2018)
Current tarball structure
The text was updated successfully, but these errors were encountered: