Summary: | Prerelease X versions have no AMD64 support | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Charles N. Burns <charlesnburns> |
Component: | New packages | Assignee: | AMD64 Project <amd64> |
Status: | RESOLVED WONTFIX | ||
Severity: | trivial | CC: | x11 |
Priority: | Lowest | ||
Version: | 1.4 | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Charles N. Burns
2004-01-04 01:25:32 UTC
With the release of xfree-4.4 coming up very soon, I think it's premature to unmask a snapshot. I am having spyderous patch it properly for amd64 though, so those who want it will have a properly working X without having to tweak it. -B I feel that it's important to get testing on as many archs as possible before the actual release of 4.4. That's one of the reasons they're in portage in the first place, albeit masked. It's not so much unmasking the port, it's adding the AMD64 keyword, at all, so that it will be available to AMD64 users who knowingly want to use beta software (using the ACCEPT_KEYWORDS="~amd64"). In its current state, even doing that does not allow anything more recent than 4.3 to be installed, because it is not marked as compatible with AMD64. sorry to disappoint you, but xfree 4.3.99.902 will not show up
in an emerge -up xfree for any arch even with
ACCEPT_KEYWORDS=~arch ....
It's in the package.mask:
amd64 profiles # cat package.mask | grep xfree
# xfree development series
>=x11-base/xfree-4.3.99
Sorry to disappoint you. Just adding ~amd64 at this point doesn't mean
anything... None the less, I had spyderous add patches to this release
that make it behave properly on amd64, and had the ~amd64 flag added,
so when we get a stable 4.4 release he doesn't forget to tag it.
-Brad
|