Opened 17 years ago
#55 new Feature request
gatherer/builder/merger pattern
| Reported by: | Owned by: | arnault | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | c. Core | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | OS: | All | |
| If Other, could you precise: | Experiment: | Other | |
| If Other, could you precise: | |||
| Stack trace: | |||
| Steps to reproduce: | |||
Description
Hi,
It would be very useful to have a pattern which would collect a bunch of 'object' files which would create a master 'target' file, spanning packages boundaries and (possible) projects boundaries.
Let say I have the following pattern: apply_pattern my_ascii_file_builder $(some_parameter) which produces an ascii_xyz.dat file and install it under eg. $(tag)/ascii_xyz.dat
So package A produces ascii_A.dat, package B -> ascii_B.dat ... etc...
This is all well and good but not very AFS friendly when the application has to open/stat all these scattered over AFS files.
The proposed gatherer/merger pattern would then register all the 'fragment' ascii_xyz.dat files and would generate a target 'ascii_$(project).dat' (regenerated each time one of the ascii_xyz.dat file has been modified).
Real world applications:
- the so-called rootmap files (which describe components for the Reflex::PluginMgr)
- in fact, merging every plugin file at the project level
So, for which release :) ?
Cheers, Sebastien.
