Hello Ronald,

thanks for the comments...  :-)

I think I will take another approach to build eclipse in future on FreeBSD.  About 2-3 year ago I made a lot patches to make version 4.32 work - the previous one was 4.24.  It took a lot of hours.  After months someone took over and created a github repository with FreeBSD stuff, which I took as the basis.  The maintainer of that repo also creates *.tar.gz files which contain a full FreeBSD compilation / package, but not usable the pkg way.  So why recompile?  I want to take his *.tar.gz file, extract and do the needed post-install steps.  The end should a "normal" package usable for FreeBSD :-)

The first steps of this approach seems to work...  I would like to check before I submit and before other people would confirm, that it works.

What do you think?  This way is more easy and does not use a long compilation time - just seconds for download and prepare.  And it is less error lasting ;-)

Of course I will depend on this github repository and data.  But that I did the last versions, too...

Regards, Norbert

On 3/13/26 13:52, Ronald Klop wrote:
Rereading your mail I saw some more concerns you mention.

1. When developing your port for main it can be easier to install dependencies for main also. That gives consistency to what is upstream. 2. As long as the maintainer of maven39 does not merge the changes to the quarterly branch, you don't need to do anything for quarterly. But keep the 4.38 tag unchanged in github. 3. Your https://github.com/NorbertXYZ/eclipse repo has a nice README.md, maybe add something similar to the eclipse-maven repo with instructions to your future self on how you did things. 😀 I totally recognize going back to some project years later and wondering how things worked.

If you get stuck, there are probably some people here or on java@ that want to help further.

NB: it can really help to keep ports@ in the cc:, if you want feedback from others too.

Regards,
Ronald.

*Van:* Norbert Grundmann <[email protected]>
*Datum:* vrijdag, 13 maart 2026 13:37
*Aan:* Ronald Klop <[email protected]>
*Onderwerp:* Re: Question for java/eclipse build

    Thanks a lot :-) :-) I will see...
    On 3/13/26 13:35, Ronald Klop wrote:

        Hi,

        cc-ing ports@ back into the conversation

        *Van:* Norbert Grundmann <[email protected]>
        *Datum:* vrijdag, 13 maart 2026 12:46
        *Aan:* Ronald Klop <[email protected]>
        *Onderwerp:* Re: Question for java/eclipse build

            On 3/13/26 08:51, Ronald Klop wrote:
            > The java/eclipse/Makefile has this comment:
            >
            > # The github repositories.  The repository under
            NorbertXYZ is for a > predefined maven
            > # download, so the build does not need to download while
            do-build is > running
            >
            > I think the port needs an updated NorbertXYZ.
            >
            > Regards,
            > Ronald

            Thank you - that is the reason...  I can see this in
            freshports on the internet...

            But how to handle this?  So I have jails to test my
            eclipse on aarch64 and amd64.  It runs 14-RELEASE-p9 and
            uses preinstalled quaterly packages - that means also the
            "older" maven39 port.  My question is: if I would install
            the newest packages from latest - would it fix the
            problem?  But what happens with poudiere runs for the
            quaterly packages.  They would need "older" maven39, or? 
            and if I use software, I install packages from quaterly. 
            I am a bit confused about how to proceed...

            All the best, Norbert :-)

-- I love penguins at the south pole, windows in my house and
            apples on my tree, but not in my computer :)
            
------------------------------------------------------------------------



        Your GH_TUPLE line defines a specific tag to use, which is now
        the same as DISTVERSION (4.38).
        NorbertXYZ:eclipse-maven:${DISTVERSION}:n

        A possible solution is to create a new tag in github (4.38_2)
        and use that in the main port and leave the quarterly port
        unchanged.
        NorbertXYZ:eclipse-maven:${DISTVERSION}_2:n
        See: https://github.com/NorbertXYZ/eclipse-maven/tags

        I hope this helps.

        Regards,
        Ronald.

-- I love penguins at the south pole, windows in my house and apples on my tree, but not in my computer :)



--
I love penguins at the south pole, windows in my house and apples on my tree, 
but not in my computer :)

Reply via email to