I've taken care of the first two points. The first by implementing a use_upstream config switched (defaults to false), when switched to true a clean up will take place and upstream will installed - vice versa. The second item was just me scratching around when troubleshooting.
---
We talked about what do to for templating and nothing solid came out of the discussion. The current EOF methods work for now, anything bigger than this and a light weight engine will probably be required. I attempted to write one in bash and fell just a few inches short when I found out I couldn't pass assoc arrays!
Renamed, env is now used for environment (upstream/package) specific switching
I still need to look into this, as of right now it works fine but I'll open a bug against the package to look into this as long as it's not a blocker.
It doesn't appear that's something readily available in PMA.
Hi Mark,
I've taken care of the first two points. The first by implementing a use_upstream config switched (defaults to false), when switched to true a clean up will take place and upstream will installed - vice versa. The second item was just me scratching around when troubleshooting.
---
We talked about what do to for templating and nothing solid came out of the discussion. The current EOF methods work for now, anything bigger than this and a light weight engine will probably be required. I attempted to write one in bash and fell just a few inches short when I found out I couldn't pass assoc arrays!
Renamed, env is now used for environment (upstream/package) specific switching
I still need to look into this, as of right now it works fine but I'll open a bug against the package to look into this as long as it's not a blocker.
It doesn't appear that's something readily available in PMA.
Thanks!