If it wasn't clear, I was basically agreeing with what you had said and was against the "Requires: >= 2.3" entry.
As far as passing an environment variable... I read your original message but I wasn't too clear on your intent. Pass it at build time? Pass it at install time? Not sure what you're trying to do exactly. ----- Original Message ----- From: "Jason R. Mastaler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, February 12, 2004 2:31 PM Subject: Re: CVS: tmda/contrib tmda.spec,1.91,1.92 > Bernard Johnson <[EMAIL PROTECTED]> writes: > > > If you add a: > > Requires: python >= 2.3 > > > > Then there must be a python package on the system (not python2.3 > > like at python.org) and that version must be 2.3 or greater, with no > > other python package installed. > > Right, which is why I said that this wasn't a good idea. > > Currently I'm requiring '/usr/bin/python2.3', not a package called > python. > > Thus, you can install a python2.3 package from python.org to satisfy > the dependency, and not conflict with your other packages. If your > python package happens to be v2.3 as in bleeding edge versions of > Redhat, you are fine as well. > > The only question is how to handle things once Python 2.4 becomes > available. > > What do you think about my idea of passing in an environment variable > to override the /usr/bin/python2.3 requirement? Have you seen this > kind of thing done before? > _________________________________________________ > tmda-workers mailing list ([EMAIL PROTECTED]) > http://tmda.net/lists/listinfo/tmda-workers _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
