Fwd: Re: IcedTea build instructions

Jiri Vanek jvanek at redhat.com
Thu Oct 6 03:39:35 PDT 2011

On 10/06/2011 12:07 PM, Andrew Haley wrote:
> On 10/06/2011 10:50 AM, Jiri Vanek wrote:
>>   >  On 10/06/2011 11:21 AM, Andrew Haley wrote:
>>> On 10/06/2011 08:53 AM, Jiri Vanek wrote:
>>>> On 10/05/2011 05:13 PM, Andrew Haley wrote:
>>>>> On 10/05/2011 04:08 PM, Andrew Haley wrote:
>>>>>>>    http://icedtea.classpath.org/wiki/Main_Page  sez:
>>>>>>>       hg clone -r icedtea6-1.10 http://icedtea.classpath.org/hg/release/icedtea6-1.10
>>>>>>>    Surely this is wrong -- you really want
>>>>>>>       hg clone -r icedtea6-1.10.3 ssh://icedtea.classpath.org/hg/release/icedtea6-1.10
>>>>> I meant http://icedtea.classpath.org/hg/release/icedtea6-1.10
>>>>>>>    Don't you?
>>>>>>>    Or maybe even
>>>>>>>       hg clone http://icedtea.classpath.org/hg/release/icedtea6-1.10
>>>> I believe the last one is the most correct. The first is also correct.
>>> How is the first one correct?  It's an old release on the
>>> icedtea6-1.10 branch.
>>>> But hg clone -r icedtea6-1.10.3 http://icedtea.classpath.org/hg/release/icedtea6-1.10 is not correct
>>>> for sure. As far as I know there is no branching on
>>>> minor-minor-vrsions - and have no sense.
>>> I'm not sure what you mean by this.  icedtea6-1.10.3 is the most
>>> recent release tag.
>> Yes - it is tagged, but not branched.
> So, please explain why you said
>    hg clone -r icedtea6-1.10.3 http://icedtea.classpath.org/hg/release/icedtea6-1.10
> is not correct.  I don't understand.  What is not correct about it?

Sorry for confusion. I believe it was explained lower "...are not dedicated for pushing (probably also not even for checking out)..."
I wasn'to understand why you wanted nust the exact tagged version.

>>>> X.Y.Z - Y is always branched, but Z just signify that in this point
>>>> tarbals (for rpms...) were released.
>>> icedtea6-1.10   is 2487:9f4eced56544
>>> icedtea6-1.10.3 is 2531:7ba3ed55131e
>>> Why are we telling people to check out an obsolete release?  It
>>> doesn't make any sense.
>> IMHO - checkout from hg clone
>> http://icedtea.classpath.org/hg/release/icedtea6-1.10 will checkout
>> nearest future release (in this case 4).
> Right.
>> Although you can checkout this earlier "Z" release, it should be
>> forever equals with stored tarball stored somewhere (eg Z=2<=>
>> icedtea6-1.10.2.tar.gz...).  This "tagged ones" are not dedicated
>> for pushing (probably also not even for checking out) as there are
>> no fixes for exact x.y.z version. All fixes go to whole branch and
>> are delivered as next "Z" release. In this case fixes for 10.1,2,3
>> are going to head of 1.10 and will be delivered in 10.4.
> Indeed.  But the question is still not answered.  What shall we tell
> people to do?  IMO, check out the latest release, which is
> icedtea6-1.10.3, or checkout the latest release branch.  I can see the
> arguments for both.  But telling people to checkout -r icedtea6-1.10
> is pretty stupid, IMO.

I got your point now. In this case the answer is to be more verbose on wiki and to describe diferences between head, releases  and -r icedtea6-1.10.Z:

First either download a released version of IcedTea6 (http://icedtea.classpath.org/download/source/) or obtain it from the Mercurial repositories. With a Mercurial checkout, you must first generate the autotools machinery.

hg clone -r icedtea6-1.10.Z http://icedtea.classpath.org/hg/release/icedtea6-1.10  (where Z is latest released minor version)
cd icedtea6-1.10

For a bleeding-edge version of IcedTea6, use http://icedtea.classpath.org/hg/icedtea6 (the next major release) or http://icedtea.classpath.org/hg/icedtea6-hg (works against the OpenJDK6 Mercurial forest) instead. For IcedTea7, use http://icedtea.classpath.org/hg/icedtea.
In case you wan to provide fix which belongs just to already released version, use "hg clone http://icedtea.classpath.org/hg/release/icedtea6-1.10" which is head of this release and changes done here will be public in next release of 1.10. (Z+1). Please Note that when cloned with -r icedtea6-1.10.Z, the repository should remains read-only.
To build IcedTea:


Or maybe even more verbose.


> Andrew.

More information about the distro-pkg-dev mailing list