From: "Dirk Schönberger" <dirk.schoenberger@sz-online.de>
To: gentoo-osx@lists.gentoo.org
Subject: Re: [gentoo-osx] Gentoo-OSX and Mac system / frameworks
Date: Wed, 15 Feb 2006 09:30:05 +0100 (CET) [thread overview]
Message-ID: <59324.84.179.246.4.1139992205.squirrel@mail.sz-online.de> (raw)
In-Reply-To: <43F2A5D3.30807@gentoo.org>
>
> OK. This is my first stab at an ebuild for creating frameworks. This
> is my first eclass, so please (kindly) point out my ignorance in the
> matter. It is still very untested; help me get this thing going before
> I submit it to gentoo-dev.
>
> The code is in my darcs-managed overlay:
> http://code.sbbod.net/portage-overlay/eclass/BPFramework.eclass
> --
I just shortly looked at it and I don't know all intricacies, but I see
the use of {PV}.
I real frameworks, a new version of the headers or libraries is assumed to
be installed if "major changes", i.e. source incompatible API changes,
occur. IIRC, {PV} changes with each new minor version or -r version? So
this may possibly create too many versions. Does there exist a variable
which changes less often, or should there be introduced such a variable?
Regards
Dirk
--
gentoo-osx@gentoo.org mailing list
next prev parent reply other threads:[~2006-02-15 8:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1F43BJ-0004gu-AY@nuthatch.gentoo.org>
2006-02-01 22:06 ` [gentoo-osx] Gentoo-OSX and Mac system / frameworks Dirk Schönberger
2006-02-01 22:48 ` Kito
2006-02-01 23:03 ` Dirk Schönberger
2006-02-01 23:51 ` Kito
2006-02-02 14:18 ` Dirk Schönberger
2006-02-07 15:24 ` Nick Dimiduk
2006-02-07 16:02 ` Grobian
2006-02-15 3:53 ` Nick Dimiduk
2006-02-15 8:30 ` Dirk Schönberger [this message]
2006-02-16 15:09 ` Nick Dimiduk
2006-02-16 17:20 ` Kito
2006-02-16 17:19 ` Kito
2006-02-16 17:24 ` Kito
2006-02-16 23:17 ` Nick Dimiduk
2005-09-30 19:12 ` [gentoo-osx] What is gentoo-osx? J.A.
2006-02-17 16:49 ` Grobian
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=59324.84.179.246.4.1139992205.squirrel@mail.sz-online.de \
--to=dirk.schoenberger@sz-online.de \
--cc=gentoo-osx@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