On Thu, 12 Nov 2009 17:45:38 +1100, Matt Michalowski
> 2009/11/12 Jeremy Olexa <email@example.com>:
>> On Wed, 11 Nov 2009 18:48:41 -0500, Michael Yang <yangofzeal@...>
>>>> since this one is straight from gx86, you'll have to look at it in
>>>> Attic of the main tree:
>>> thanks - it worked.
>>> If there were significant alterations to make it work in prefix, would
>>> there be a similar attic for prefix ebuilds?
>> Everything we do is in source control. You found the CVS attic. One way
>> achieve the same on the svn repo is to mess around with the web
>> (trac) or just do svn up -r <rev num>.
>> trac: http://overlays.gentoo.org/proj/alt/browser/trunk/prefix-overlay/
>> repo: http://overlays.gentoo.org/svn/proj/alt/trunk/prefix-overlay/
> Can I just ask how things make it from the SVN repository to the rsync
As we migrate completely to gx86, there is a whitelist.txt file in the svn
repo. Items in this whitelist file are pulled from gx86 completely,
Files in the svn overlay are pulled into the rsync tree.
End goal, no svn overlay...all in gx86 (CVS)
> For example, in my current rsync tree, there are dev-db/tokyocabinet
> ebuilds. These don't exist in the prefix-overlay SVN tree, but look
> like they come straight from the gx86 tree. They don't have ~x86-linux
Probably because they were never tested on ~x86-linux or ~amd64-linux. If
it works, please file a bug to get the keyword added.
> or ~amd64-linux keywords, but rather just ~x86 and ~amd64. Is it now
> possible or even recommended to just put ~x86/~amd64 in
Hope that helps. :)