SRU Delima , suggestions requested

[Scott Kitterman]

On Saturday 15 December 2007 09:47, Brandon Holtsclaw wrote:
> OK we all hate binary non-floss programs but all that aside, I have come
> across a unique problem with a proposed SRU to flashplugin-nonfree that
> I would welcome any help/sugestions with, after a short disscussion on
> IRC about it here is the problem and 4 possible outcomes.
>
> -------
>
> [ Backstory ]
> flashplugin-nonfree has been updated upstream to version 9,0,115,0 , the
> way this package works is it downloads from a stable URL on the adobe
> site that contains the current release, checks the md5 of this tarbal
> and then installs it via postinst
>
> [ Problem ]
> 9,0,115,0 is *known* to break konqueror but works as intended on
> FireFox, the reason for this is konqueror does not support XEmbed
>
> [ Solution 1 ]
> Dont update , leave both firefox and konq broken on dapper to gutsy for
> new installs ( existing installs should be fine because the package has
> already downloaded the old tar and installed it )
>
> [ Solution 2 ]
> Update and knowingly break konq in dapper --> gutsy for people that have
> flash installed ( i'm guessing a high percentage )
>
> [ Solution 3 ]
> Update + SRU an patch for konq to add XEmbed, this patch will alow konq
> to use the newer flash and wont look like a regression to users
> ( proposed patch from Novel, not upstream yet
> https://bugzilla.novell.com/show_bug.cgi?id=348088 ) but is pretty
> invasive imho for a SRU
>
> [ Solution 4 ]
> Adobe provides older versions for download also but anything that is not
> the current version is lumped into a 60+MB archive, the package could be
> updated on dapper --> gutsy to grab this archive and extract + md5 check
> the older 9,0,48,0 release and install it
> (
> http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_14266&sliceId=
>2 )
>
> ---------
>
> IMHO solutions 1 to 3 arent options IMHO and 4 is the "safest" route but
> has two major side effects, 1) the packaging will change quite a bit for
> an SRU 2) its a 60+MB download, while for me this isnt a problem but for
> those in other situations without broadband or download caps ( .au comes
> to mind ) this might not be idea , even with those two issues i think
> this outweighs the 1 to 3 options.
>
> suggestions welcome, even if its a simple +/-1 for an option as to help
> me decide what to do ...
>

My suggestion would be to get the Konqueror changes uploaded to Hardy ASAP and 
get some testing done with them.  This will need to be done in any case and 
will help inform the final decision.

Since Hardy and Gutsy are both KDE 3.5.8, I think successful testing in Hardy 
would go a long way to mitigate the risk of a Konqueror SRU in Gutsy.  Less 
true for the earlier releases.

Personally, I'd lean towards option 3 for Gutsy and 4 for Dapper/Edgy/Feisty.

Scott K