jds SVN: spec-files

[Brian Cameron]

Patrick:

> I understand what you're saying regarding the SUNWgnutls
> responsibility movement. However, the problem is we didn't bump up
> SUNWgnutls but gnome-gtkhtml (SUNWgnome-libs component) which goes bad
> on a missing item that should be shipped by SUNWgnutls (damien is
> doing some tests I read when I was at the airport, we might have
> missed a configure flag).
> 
> Nevertheless, just for my understanding. Does this mean that any
> package upgrade of any JDS component that depends on a newer version
> of $software-with-encryption is blocked until
> $software-with-encryption is reviewed? I'd like to know this for
> future reference where I might get even more involved with the trunk
> build ;)

In the past we have bumped the version in the spec-file as needed to
make the development/head build work.  Then we complete the
paperwork before we integrate into Nevada (which we typically do when
soon after the stable/even-numbered release is made).

However, I'd recommend that we avoid module upgrade of any JDS
components that include encryption until after we transfer these
modules to the other team.  Hopefully this won't take long.

If an issue comes up that forces us to update these modules, that
probably won't be a problem.  It will likely just mean more paperwork.

Brian