Re: intention for tiff packages

2012-01-24 Thread Julien Cristau
On Tue, Jan 24, 2012 at 14:00:33 -0500, Jay Berkenbilt wrote: > Julien Cristau wrote: > > > On Mon, Jan 23, 2012 at 11:00:53 -0500, Jay Berkenbilt wrote: > > > >> Upstream has committed symbol versioning for both the 3.9.x branch and > >> the trunk (4.0.0) and is prepared to release 3.9.6 and 4.

Re: intention for tiff packages

2012-01-24 Thread Jay Berkenbilt
Julien Cristau wrote: > On Mon, Jan 23, 2012 at 11:00:53 -0500, Jay Berkenbilt wrote: > >> Upstream has committed symbol versioning for both the 3.9.x branch and >> the trunk (4.0.0) and is prepared to release 3.9.6 and 4.0.1 with symbol >> versioning once we sign off that it's what we're looking

Re: intention for tiff packages

2012-01-23 Thread Julien Cristau
On Mon, Jan 23, 2012 at 11:00:53 -0500, Jay Berkenbilt wrote: > Upstream has committed symbol versioning for both the 3.9.x branch and > the trunk (4.0.0) and is prepared to release 3.9.6 and 4.0.1 with symbol > versioning once we sign off that it's what we're looking for. What's > the best way t

Re: intention for tiff packages

2012-01-23 Thread Julien Cristau
On Sun, Jan 22, 2012 at 20:46:11 -0500, Jay Berkenbilt wrote: > Much to my surprise, upstream looks like they are going to take it. I > started a thread on the tiff list today, and one of the primary > maintainers already introduced a change in their CVS to make this > possible. > Awesome news,

Re: intention for tiff packages

2012-01-23 Thread Jay Berkenbilt
Jay Berkenbilt wrote: > Julien Cristau wrote: > >> On Sat, Jan 21, 2012 at 19:10:00 -0500, Jay Berkenbilt wrote: >> >>> Julien Cristau wrote: >>> >>> > As I said previously, if versioned symbols don't happen (in both the old >>> > and new versions), then the transition is unlikely to happen to

Re: intention for tiff packages

2012-01-22 Thread Jay Berkenbilt
Julien Cristau wrote: > On Sat, Jan 21, 2012 at 19:10:00 -0500, Jay Berkenbilt wrote: > >> Julien Cristau wrote: >> >> > As I said previously, if versioned symbols don't happen (in both the old >> > and new versions), then the transition is unlikely to happen too. It >> > was done for png and

Re: intention for tiff packages

2012-01-22 Thread Julien Cristau
On Sat, Jan 21, 2012 at 19:10:00 -0500, Jay Berkenbilt wrote: > Julien Cristau wrote: > > > As I said previously, if versioned symbols don't happen (in both the old > > and new versions), then the transition is unlikely to happen too. It > > was done for png and jpeg, so it's not like it'd be a

Re: intention for tiff packages

2012-01-22 Thread Jay Berkenbilt
Jay Berkenbilt wrote: >> As I said previously, if versioned symbols don't happen (in both the old >> and new versions), then the transition is unlikely to happen too. It >> was done for png and jpeg, so it's not like it'd be a first. > > I have the skills to do this and understand the concept, b

Re: intention for tiff packages

2012-01-21 Thread Jay Berkenbilt
Julien Cristau wrote: Okay, I basically have to admit that I agree with everything you said. >> Proposed new state: >> >> * Upgrade the tiff package to 4.0.0-1 and upload to unstable. No other >>changes would be made to the package. >> >> * Create source package tiff3 in section oldlibs a

Re: intention for tiff packages

2012-01-21 Thread Julien Cristau
On Sat, Jan 21, 2012 at 11:38:10 -0500, Jay Berkenbilt wrote: > Here's what I'd like to do with the tiff packages. I believe this will > be relatively non-disruptive. Technically, I don't think I *have* to > ask permission for this, but I want to do it as a courtesy to the > release team, to giv

intention for tiff packages

2012-01-21 Thread Jay Berkenbilt
Here's what I'd like to do with the tiff packages. I believe this will be relatively non-disruptive. Technically, I don't think I *have* to ask permission for this, but I want to do it as a courtesy to the release team, to give you the chance to suggest a different approach or influence the timin