cvs commit: ports/www/firefox15 Makefile distinfo
Jeremy Messenger
mezz7 at cox.net
Thu Nov 9 21:32:39 UTC 2006
On Thu, 09 Nov 2006 15:23:07 -0600, Joe Marcus Clarke <marcus at FreeBSD.org>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jeremy Messenger wrote:
>> On Thu, 09 Nov 2006 15:04:20 -0600, Kris Kennaway <kris at obsecurity.org>
>> wrote:
>>
>>> On Thu, Nov 09, 2006 at 02:54:18PM -0600, Jeremy Messenger wrote:
>>>> On Thu, 09 Nov 2006 14:29:52 -0600, Simon L. Nielsen
>>>> <simon at FreeBSD.org>
>>>> wrote:
>>>>
>>>> >On 2006.11.09 19:17:41 +0000, Michael Johnson wrote:
>>>> >>ahze 2006-11-09 19:17:41 UTC
>>>> >>
>>>> >> FreeBSD ports repository
>>>> >>
>>>> >> Modified files:
>>>> >> www/firefox15 Makefile distinfo
>>>> >> Log:
>>>> >> - Update to 1.5.0.8
>>>> >> - Mark DEPRECATED by Firefox 2.0
>>>> >
>>>> >We need to find some way to get this into 6.2... unfortunately since
>>>> >6.2 contains firefox 1.5 as www/firefox I'm not really sure how to do
>>>> >this. I talked a bit to kris about this on IRC today, but the only
>>>> >way there really seem to be to do this (which don't involve nasty
>>>> >hacks) was to add firefox 1.5.0.8 as www/firefox temporarily and then
>>>> >re-adding 2.0 as www/firefox there...
>>>> >
>>>> >Anybody got any better ideas?
>>>>
>>>> I don't know what 1.5.0.8 has, but if there has some serious security
>>>> issue fix in 1.5.0.8 then it's ok with me. As for 2.0, I disagree for
>>>> to
>>>> get it in 6.2. It's not ready and not have the same level of
>>>> stability as
>>>> in 1.5.x.
>>>
>>> Yep, the question is how to manage getting a 1.5 version of
>>> www/firefox into 6.2, since the port was already spammed by the 2.0
>>> update.
>>
>> Commit in the RELENG_6_2_0 of ports tree, then rebuild all ports depend
>> on firefox. Will that work?
>
> RELEASE_6_2_0 is a tag not a branch. That's enough about branching the
> ports tree.
>
>>
>> If it is not possible to commit in the RELENG_6_2_0, then do the
>> checkout RELENG_6_2_0 and tweak in www/firefox before start to rebuild
>> all ports depend on firefox. I know that will working with MarcusCom
>> Tinderbox, but I don't know what about with your tinderbox.
>
> That will work for package building, but not for preserving the sanctity
> of release. We need to be able to checkout the ports that shipped with
> 6.2 well into the year 2038.
Good poing, never thought of that...
Cheers,
Mezz
> Joe
>
> - --
> Joe Marcus Clarke
> FreeBSD GNOME Team :: gnome at FreeBSD.org
> FreeNode / #freebsd-gnome
> http://www.FreeBSD.org/gnome
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFFU5w7b2iPiv4Uz4cRAgEkAJ0ULhTe8xkSm2uB02/8OsZTELPY5wCgi3KH
> fCu2a2/JVwT6gFg+J6KkFc8=
> =DaM1
> -----END PGP SIGNATURE-----
--
mezz7 at cox.net - mezz at FreeBSD.org
FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/ - gnome at FreeBSD.org
http://wiki.freebsd.org/multimedia - multimedia at FreeBSD.org
More information about the freebsd-gnome
mailing list