public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marat Radchenko <slonopotamusorama@gmail.com>
To: gentoo-java@lists.gentoo.org
Subject: [gentoo-java] Ebuilds for IntelliJ IDEA
Date: Tue, 22 Dec 2009 11:15:11 +0300	[thread overview]
Message-ID: <b944a51b0912220015q4eb17f38y3d58fcb0838a6185@mail.gmail.com> (raw)

Hi. I've been bumping IntelliJ IDEA ebuild [1] for a pretty long time
and everyone was happy. Now, idea-9 released. I already bumped
dev-util/idea ebuild which now builds Ultimate Edition (UE).

The question is how we want to handle Community Edition (CE) [2]
(available under Apache-2.0 license). Jetbrains shipped binary release
[3], source is available via git [4,5], however there isn't any source
tarball.

I suggest following layout: dev-util/idea (UE) +
dev-util/idea-community (source CE) [+ dev-util/idea-community-bin
(binary CE)] where idea-community-bin is optional. The goal in mind is
to push source CE into main tree.

Another question is how to handle simultanious installations of
different versions. dev-util/idea is SLOTed based on major version
(idea has separate config dir in ~ for each major version) and
installed to /opt/idea-${SLOT} with /usr/bin/idea-${SLOT} launcher
script.

The last question is what to do with source CE tarballs since upstream
doesn't publish them (although, git tags to make them ourselves are
available)

[1] http://overlays.gentoo.org/proj/java/browser/java-experimental/dev-util/idea
[2] http://www.jetbrains.org/display/IJOS/Home
[3] http://www.jetbrains.com/idea/download/index.html
[4] http://www.jetbrains.org/pages/viewpage.action?pageId=983225
[5] http://git.jetbrains.org/?p=idea/community.git



             reply	other threads:[~2009-12-22  8:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22  8:15 Marat Radchenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-03-30 21:24 [gentoo-java] Ebuilds for IntelliJ IDEA blangel

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=b944a51b0912220015q4eb17f38y3d58fcb0838a6185@mail.gmail.com \
    --to=slonopotamusorama@gmail.com \
    --cc=gentoo-java@lists.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