public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Kevin Brace <kevinbrace@gmx.com>
To: Sam James <sam@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Updating community maintained Gentoo Eclipse IDE repository ebuild to EAPI 7
Date: Fri, 20 Sep 2024 05:00:32 +0200	[thread overview]
Message-ID: <trinity-1b242cb9-a2c7-4248-97ad-4741ee38d3d0-1726801232146@3c-app-mailcom-bs06> (raw)
In-Reply-To: <878qvnaw9j.fsf@gentoo.org>

Hi Sam,

Okay, if I was not clear about what I wanted, I will try to clarify.
I personally wanted the "sort of official" Eclipse IDE Gentoo overlay on GitHub to take up my updated EAPI 7 based ebuilds, but the only person I was able to contact  refused.
I call the repository "sort of official" since it is still on the Gentoo wiki page. [1]
I fixed the ebuild so I do not feel like it should be rejected by the developer, but it is what it is.
Since this is what the situation is, I feel like the existing "sort of official" Eclipse IDE Gentoo overlay should be forked, and the updated ebuilds should be incorporated.
Or, perhaps I can gain access to commit the updates to this repository, but I assume the people listed on the GitHub page probably will not allow that.
I hope the explanation I wrote here makes sense.
I was not aware of the alternative unofficial repository .
I will take a look at it.
That being said, the wiki page still has the now broken repository. [2]
Something needs to be done to remedy the situation.

Regards,

Kevin Brace
Brace Computer Laboratory blog
https://bracecomputerlab.com


[1]: https://wiki.gentoo.org/wiki/Eclipse
[2]: https://github.com/gentoo/eclipse-overlay


> Sent: Thursday, September 19, 2024 at 7:34 PM
> From: "Sam James" <sam@gentoo.org>
> To: "Kevin Brace" <kevinbrace@gmx.com>
> Cc: gentoo-dev@lists.gentoo.org
> Subject: Re: [gentoo-dev] Updating community maintained Gentoo Eclipse IDE repository ebuild to EAPI 7
>
> Kevin Brace <kevinbrace@gmx.com> writes:
>
> > Hi,
> Hi,
>
> >
> > I am a first time poster who just subscribed to the gentoo-dev mailing list.
> > I installed Eclipse IDE 4.6 to one Gentoo Linux installation using the
> > community maintained Eclipse IDE repository ebuild when Portage still
> > supported EAPI 6, but the current release of Portage no longer does
> > so.
> > I have been increasingly annoyed by this community maintained Gentoo Eclipse IDE ebuild giving me weird warning type messages when running Portage.
> > Of course, it does not stop Portage from running, but I do not like it aesthetically.
> > The cause of the warning messages are that ebuilds are still at EAPI 5 (for Eclipse IDE 4.5) and 6 (for Eclipse IDE 4.6), and they need to be updated to at least EAPI 7.
> > I got so annoyed by this that I decided to take them into my own hands, and I managed to update ebuilds in question.
> > I got rid of all the annoying messages displayed when running Portage, and it appears that Eclipse IDE installs fine.
> > So I directly contacted one developer of the three still active on GitHub, but he refused to take up the ebuilds and update them.
> > He does not seem to want to maintain the repository any longer (he
> > appears to be disillusioned with the Eclipse IDE ebuilds they
> > developed for some reason), and even suggested that a new community
> > repository to be created to replace the now obsolete Eclipse IDE
> > repository.
> > This one I am talking about.
> >
> > https://github.com/gentoo/eclipse-overlay
> >
> > Personally, I really did not want to get involved in this type of OS
> > infrastructure project because I work on totally different type of
> > code development projects, but I feel like something has to be done to
> > update the Eclipse IDE ebuilds to keep up with Portage.
> > Let me know what more experienced Gentoo developers think.
>
> In general, packaging Java is pretty painful and everyone has migrated
> to using just prebuilt jars for useful applications (like Eclipse).
>
> (See
> e.g. https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/4EHBACT4I263R4QF75HB3DUJWWANGHAS/,
> and I think Chewi wrote a similar email at one point.)
>
> I'm not 100% clear what's being requested here:
> * it definitely looks like the eclipse overlay is pretty dead and
>   should probably be removed from the repository list;
> * we can consider requests if someone wants access to it (perhaps you!)
>   to contribute fixed ebuilds to it, but it might just be better to make
>   your own repository for that;
> * there seem to be some newer ebuilds for eclipse in other repositories,
>   see e.g. http://gpo.zugaina.org/Search?search=eclipse
>
> >
> > Regards,
> >
> > Kevin Brace
> > Brace Computer Laboratory blog
> > https://bracecomputerlab.com
>
> thanks,
> sam
>
>


  reply	other threads:[~2024-09-20  3:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20  1:46 [gentoo-dev] Updating community maintained Gentoo Eclipse IDE repository ebuild to EAPI 7 Kevin Brace
2024-09-20  2:34 ` Sam James
2024-09-20  3:00   ` Kevin Brace [this message]
2024-09-20  3:13     ` James Stevenson
2024-09-20  3:29     ` Eli Schwartz
2024-09-24  9:33       ` Filip Kobierski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-1b242cb9-a2c7-4248-97ad-4741ee38d3d0-1726801232146@3c-app-mailcom-bs06 \
    --to=kevinbrace@gmx.com \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=sam@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox