On Fri, Apr 13, 2012 at 04:02:47PM +0200, Johannes Renner wrote:
> On 04/11/2012 02:28 PM, Jan Pazdziora wrote:
> >
> > How about having a new database table with prefixes and replacements,
> > where the prefix could be empty (NULL) to mean prepend. Record with
> > the longest matching prefix would provide the replacement string.
> >
> > This way you'd be able to have sane defaults in Spacewalk and every
> > downstream product could customize this mapping table to meet their
> > business requirements.
>
> Did I get that right, the table for RH would look like this:
>
> Prefix | Replacement
> --------------------
> RH | CL
> CL | CM
> CM | CN
> CN | CO
Or even
RHBA- CLBA-
RHSA- CLSA-
RHEA- CLEA-
...
to be on the safer side.
> ... | ...
>
> While for us it would look like this:
>
> <NULL> | CL-
> CL | CM
> CM | CN
> CN | CO
> ... | ...
Or
<NULL> CL-
CL- CM-
CM- CN-
...
> When cloning, we wouldn't check if we actually have a clone already,
> but just lookup the table for the longest match and replace?
Do we currently check if a clone already exists? Anyway, I was only
proposing a naming, not a logic which determines whether to clone or
not.
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
_______________________________________________
Spacewalk-devel mailing list
Spacewalk-devel@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-devel
