public inbox for gentoo-java@lists.gentoo.org
 help / color / mirror / Atom feed
From: Joshua Nichols <nichoj@gentoo.org>
To: gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] RFC: Default src_compile for java-pkg-2.eclass
Date: Mon, 11 Dec 2006 10:04:21 -0500	[thread overview]
Message-ID: <457D7375.4060803@gentoo.org> (raw)
In-Reply-To: <457D3A0B.5090301@gentoo.org>

Vlastimil Babka wrote:
> I wonder if ebuild using those variables would be more typing than
> ebuild with own src_compile() :) but not a bad idea anyway.
>
>   
The idea is that you don't end up repeating the same code snippet over 
and over. Instead, you use some variables to configure what targets get 
called. This helps with maintainence, as if we change src_compile, you 
don't have to update it in a trillion places. For example, eant dies by 
itself on error, but a lot of places do eant || die. If we had a default 
src_compile, you'd have to fix it in exactly one place.
> Yeah check is needed, otherwise you'll be trying to compile current -bin
> packages without src_compile() in ebuild...
> Not sure if any ebuild would use the variable, but why not...
>   
The answer to 'why not' would be added complexity. But some packages 
would use it, ie, I know some packages have build files at, for example 
'build/build.xml'.

-- 
Joshua Nichols
Gentoo/Java - Project Lead

-- 
gentoo-java@gentoo.org mailing list



  reply	other threads:[~2006-12-11 15:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-09 12:19 [gentoo-java] RFC: Default src_compile for java-pkg-2.eclass Petteri Räty
2006-12-11  5:05 ` Joshua Nichols
2006-12-11 10:59   ` Vlastimil Babka
2006-12-11 15:04     ` Joshua Nichols [this message]
2006-12-17 16:44       ` Petteri Räty

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=457D7375.4060803@gentoo.org \
    --to=nichoj@gentoo.org \
    --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