Hi Andrew,
On September 23, 2015 6:10:31 PM GMT+02:00, Andrew Johnson <[email protected]> wrote:
...
>A couple more ideas:
>* How about assembling the snippets inside a regular src/O.<arch>
>directory and installing the output file?
That's why I want the rules in a regular RULES file and the mechanism to work for any file.
Note that the usage idea in my last mail was using st.cmd but did not have anything specific.
>* Allowing snippets to be provided by support modules listed in the
>IOC's configure/RELEASE file? How would you pick which ones (there
>might
>be architecture-specific snippets)?
If you have arch-specific snippets, you should put them in a separate directory and add that directory (for the appropriate arch) to your command line.
I just want to provide the mechanism, and not assume more than necessary about its use.
>I'm starting to think that being explicit about which files go into the
>output file might be a better approach as Torsten suggested. The IOC
>developer then has the final say as to what gets run, and nobody else
>can just add a file to the global snippets directory to have their code
>run on all IOCs — that could be really bad. Of course you can still use
>wildcards in the list if desired for your site.
Using directories (or wildcards) is the whole point of my use case.
If a new version of my global support module needs an additional line in the st.cmd, I want its RPM to drop it in the global snippets dir, rebuild my ~500 IOCs and be done with it. I do *not* want to update 500 Makefiles.
I want my configuration database exporter to populate a single directory with all generated st.cmd content (from the database) for a specific IOC, and have it merged with the developer's special snippets (under version control) without having to change the version controlled Makefile.
The global snippet dir will be a place where the system package manager drops files from RPMs. You have to be root to screw around, and if you are root... it will be as vulnerable as any file in /etc.
So:
I was thinking directories and filter patterns, but globs would work for me, too. Explicit file names - sure, why not.
I will do something that allows all reasonable use.
Maybe specifying directories should need an option, probably the no-dots restriction, too.
Thanks for your input!
~Ralph
- Replies:
- Re: RFC: Creating st.cmd from snippets Benjamin Franksen
- References:
- RFC: Creating st.cmd from snippets Ralph Lange
- Re: RFC: Creating st.cmd from snippets Andrew Johnson
- Re: RFC: Creating st.cmd from snippets Torsten Bögershausen
- Re: RFC: Creating st.cmd from snippets Ralph Lange
- Re: RFC: Creating st.cmd from snippets Andrew Johnson
- Navigate by Date:
- Prev:
Re: RFC: Creating st.cmd from snippets Andrew Johnson
- Next:
Re: RFC: Creating st.cmd from snippets Benjamin Franksen
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: RFC: Creating st.cmd from snippets Andrew Johnson
- Next:
Re: RFC: Creating st.cmd from snippets Benjamin Franksen
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|