> > > 1) send your changes to the developer of the rpm, explain the need for
the
> > > change and ask the developer if he/she is agreeable, to update their
rpm
> > > to include your changes and send you the new release.
>
> Darrell is right, but I would suggest that rather than use
> templates-custom in the interim, that you branch the conflicting package
> so that your version of that package doesn't conflict any more. Then once
> the developer of the original RPM includes your changes, you build a new
> contrib package which requires their new version, and you remove your
> branched underlying package. [Have I expressed that clearly enough?]

I think I understand. Example:
 - create e-smith-named-1.6.1-02 (now is -02) patched with modifications
needed by my package and notify e-smith
 - distribute e-smith-named-1.6.1-02 with my package explaining to install
it in sme5.0 only (for example)
 - when (and if) e-smith applies my patch to e-smith add a Requires to my
rpm for the updated e-smith-named

I could also use a Requires: e-smith-named-1.6.2 and change the name of my
patched named rpm in first step to enforce dependency on updated named.

> > Changes are incompatible this time.
> > I'm adding a config option to dhcpd.conf not supported by standard dhcp
> > version 2.
> > When you install dhcp 3, you also install e-smith-dhcp-3.
> >
> > I believe templates-custom is the only way. Charlie ?
>
> No. Why don't you have your template code check for the version of dhcp
> installed, and only output compatible stuff? Or branch our code (using a
> patch, of course) and wait for us to catch up.

When you say using a patch, do you mean rebuilding an updated rpm with a
small patch ?

Ciao,
Filippo



--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org

Reply via email to