On Tue, 15 Jul 2008, Atsuhito Kohda wrote:
> On Mon, 14 Jul 2008 17:55:42 -0700, Don Armstrong wrote:
> 
> > > Why is this "important"? It looks like a purely cosmetical question.
> > > (minor or wishlist.)
> > 
> > Because it's something that should be resolved prior to release, and
> > probably should even be RC. It certainly isn't the kind of breakage
> > that should be introduced in an NMU.
> 
> I don't know it is acceptable for you or not but, personally, I
> prefer lynx-cur because there are two branches of lynx in the
> upstream and the development version is called lynx-cur by the
> upstream. The name lynx-cur explicitly expresses that it is the
> developement version instead of stable version.

It's your decision, but are you sure that you want to take on the
repsonsibility of maintaining a development release of lynx throughout
a stable release cycle instead of the stable release of lynx?

I can't speak for the security team, but I'd be rather suprised if
they'd be willing to support a development version in favor of a
stable version of lynx.

From where I sit, it seems like the wrong solution to #369386 was
reached; lynx-cur should have an RC bug against it, but that RC bug
should exist only to keep lynx-cur to transition to testing and then
being released. A second lynx package should exist which is the most
recent stable release of the lynx tree. [This situtation already
exists for numerous -snapshot packages which should never be released
with a Debian stable release.]

An alternative possibility exists that the -cur release is actually
the version that upstream plans on having long-term support for, and
the lynx version is just for legacy users, but the bug thread (which I
read) doesn't make this point clear.


Don Armstrong

-- 
NASCAR is a Yankee conspiracy to keep you all placated so the South
won't rise again.
 -- http://www.questionablecontent.net/view.php?comic=327

http://www.donarmstrong.com              http://rzlab.ucr.edu



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to