From: Alistair Bush <alistair.bush@gmail.com>
To: Fabian Groffen <grobian@gentoo.org>, gentoo-java@lists.gentoo.org
Subject: Re: [gentoo-java] javatoolkit: new project layout
Date: Sun, 06 Jan 2008 10:29:29 +1300 [thread overview]
Message-ID: <477FF6B9.6020708@gmail.com> (raw)
In-Reply-To: <20080105123126.GG7944@gentoo.org>
Fabian Groffen wrote:
> On 06-01-2008 01:16:16 +1300, Alistair Bush wrote:
>> This email is to garner some discussion on my new project layout for
>> javatoolkit.
> [snip]
>> You can browse the repo here
>> http://overlays.gentoo.org/proj/java/browser/projects/javatoolkit/branches/layout_refactor_branch
>
> While you're at it, would it be possible to make javatoolkit a little
> bit easier for use prefix folks to maintain? We're happily running Java
> in our prefixes so any cooperation here would be greatly appreciated.
>
> We currently apply this patch:
> http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/dev-java/javatoolkit/files/0.2.0-prefix.patch
> (trac is a bit picky about it, so please look at the plain text version
> of it)
>
> As you can see, Prefix is mainly concerned with shebangs (/usr/bin/env
> python should work for everyone just fine), and with adding the offset
> prefix in the installation paths. I understand that not every path can
> be dropped, but it would be great if the make stuff could be simplified,
> by e.g. having a variable for the prefix (defaulting to /usr) such that
> we could just simply only patch that one, instead of every place, as in
> the patch.
>
> Thanks,
>
>
I believe (and hope) that the distutils src_install() will handle this.
Basically setup.py has a --root="${D}" option
as in here
distutils_src_install() {
# need this for python-2.5 + setuptools in cases where
# a package uses distutils but does not install anything
# in site-packages. (eg. dev-java/java-config-2.x)
# - liquidx (14/08/2006)
pylibdir="$(${python} -c 'from distutils.sysconfig import
get_python_lib; print get_python_lib()')"
[ -n "${pylibdir}" ] && dodir "${pylibdir}"
if has_version ">=dev-lang/python-2.3"; then
${python} setup.py install --root=${D} --no-compile "$@" || die
else
${python} setup.py install --root=${D} "$@" || die
fi
DDOCS="CHANGELOG KNOWN_BUGS MAINTAINERS PKG-INFO CONTRIBUTORS TODO NEWS"
DDOCS="${DDOCS} Change* MANIFEST* README* AUTHORS"
for doc in ${DDOCS}; do
[ -s "$doc" ] && dodoc $doc
done
[ -n "${DOCS}" ] && dodoc ${DOCS}
}
Is this acceptable?
--
gentoo-java@gentoo.org mailing list
next prev parent reply other threads:[~2008-01-05 21:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 12:16 [gentoo-java] javatoolkit: new project layout Alistair Bush
2008-01-05 12:31 ` Fabian Groffen
2008-01-05 21:29 ` Alistair Bush [this message]
2008-01-07 20:19 ` Fabian Groffen
2008-01-07 20:29 ` Petteri Räty
2008-01-07 20:42 ` Fabian Groffen
2008-01-07 23:33 ` Petteri Räty
2008-01-08 8:44 ` Fabian Groffen
2008-01-08 6:13 ` Alistair Bush
2008-01-08 8:47 ` Fabian Groffen
2008-01-09 8:49 ` Alistair Bush
2008-01-09 9:04 ` Alistair Bush
2008-01-10 5:46 ` Alistair Bush
2008-01-10 21:31 ` Vlastimil Babka
2008-01-10 23:51 ` Petteri Räty
2008-01-05 12:40 ` Vlastimil Babka
2008-01-05 21:46 ` Alistair Bush
2008-01-05 23:06 ` Alistair Bush
2008-01-05 23:21 ` Vlastimil Babka
2008-01-05 23: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=477FF6B9.6020708@gmail.com \
--to=alistair.bush@gmail.com \
--cc=gentoo-java@lists.gentoo.org \
--cc=grobian@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