On Mon, Dec 31, 2012 at 12:18 PM, Matthew Barr
wrote:
> So: should forge modules use repo's explicitly? or is there already a
> standard design pattern that implements a parameter for repos?
>
I would like to see Forge modules make the usage of a yumrepo configurable
via parameterized classes
On Monday, December 31, 2012 12:40:26 PM UTC-6, Matthew Barr wrote:
>
> I'm working with a forge module that specifies & installs a yum repo
> before it installs the packages, then goes about it's business.
> * package isn't part of a standard repo
>
> We operate on a policy of minimizing the
On 12/31/2012 03:18 PM, Matthew Barr wrote:
Sorry to reply to myself.. but option #1 doesn't work. (It works for
resources, but not classes. Silly me.)
So: should forge modules use repo's explicitly? or is there already a
standard design pattern that implements a parameter for repos?
Sorry to reply to myself.. but option #1 doesn't work. (It works for
resources, but not classes. Silly me.)
So: should forge modules use repo's explicitly? or is there already a
standard design pattern that implements a parameter for repos?
else… I guess I'll end up writing one :)
On D
