In order for portage to depend on install-xattr (see bug #465000), we need to mirror the keywordking: KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86 ~amd64-fbsd ~sparc-fbsd ~x86-fbsd" I've already done amd64 and x86. I can do mips arm ppc and ppc64, but I'll need arch teams to look at the following: TARGET_ARCHES="~alpha ~arm64 ~hppa ~ia64 ~m68k ~s390 ~sh ~sparc ~amd64-fbsd ~sparc-fbsd ~x86-fbsd" Reproducible: Always
I just tested/keyworded for ~arm ~mips ~ppc ~ppc64
alpha done
ia64 done
sparc done
x86 done
Marked ~hppa.
Ping remaining arches for keywords. Since these are unstable arches, I'm going to start a stabilization request for the stable arches. It has been in the tree a while now.
~s390 done.
Since xattr is not provied on FreeBSD (instead it provide similar feature: extattr), it'll need some work to support this package on FreeBSD.
(In reply to Naohiro Aota from comment #9) > Since xattr is not provied on FreeBSD (instead it provide similar feature: > extattr), it'll need some work to support this package on FreeBSD. Well actually, pax markings make no sense on freebsd either because pax markings are only for a pax enabled linux kernel. So the question is, how do we make portage depend on this package if USE=xattr on all but non-linux arches. Since I'm not familiar *-fbsd, how should we do this? Does USE=xattr make any sense there?
(In reply to Anthony Basile from comment #10) > (In reply to Naohiro Aota from comment #9) > > Since xattr is not provied on FreeBSD (instead it provide similar feature: > > extattr), it'll need some work to support this package on FreeBSD. > > Well actually, pax markings make no sense on freebsd either because pax > markings are only for a pax enabled linux kernel. So the question is, how > do we make portage depend on this package if USE=xattr on all but non-linux > arches. > > Since I'm not familiar *-fbsd, how should we do this? Does USE=xattr make > any sense there? Well... we *can* use extattr in some way. However, we don't have any usage for it now and we won't even plan to implement one. So there's nothing to prevent use.mask'ing the USE flag for now.
(In reply to Naohiro Aota from comment #11) > (In reply to Anthony Basile from comment #10) > > (In reply to Naohiro Aota from comment #9) > > > Since xattr is not provied on FreeBSD (instead it provide similar feature: > > > extattr), it'll need some work to support this package on FreeBSD. > > > > Well actually, pax markings make no sense on freebsd either because pax > > markings are only for a pax enabled linux kernel. So the question is, how > > do we make portage depend on this package if USE=xattr on all but non-linux > > arches. > > > > Since I'm not familiar *-fbsd, how should we do this? Does USE=xattr make > > any sense there? > > Well... we *can* use extattr in some way. However, we don't have any usage > for it now and we won't even plan to implement one. So there's nothing to > prevent use.mask'ing the USE flag for now. That works.
I just realized we also need keywordking for arm64 and m86k. cc-ing vapier who takes care of those.
Masked USE=xattr on FreeBSD
~m68k/~arm64 done
This is already ~sh. If you want it stable, please change the KEYWORDS field and cc sh again.