The ebuild merges and works properly under MacOS X with the version of Vim shipped with OSX (MacOS X version 10.4.3 build 8F46). Reproducible: Always Steps to Reproduce: 1. sudo ebuild /usr/portage/app-vim/vimcommander/vimcommander-1.54.2.2.ebuild merge Actual Results: The Vim plugin gets installed and works by calling the "VimCommanderToggle()" function. Plus, vimcommander works as expected. Expected Results: Package shouldn't be masked for ppc-macos.
Here's output from "emerge --info", I forgot to include it before: !!! Relying on the shell to locate gcc, this may break !!! DISTCC, installing gcc-config and setting your current gcc !!! profile will fix this Portage 2.0.51.22-r3 (default-darwin/macos/10.4, gcc-4.0.1, libsystem-7.1-r0, 8.3.0 Power Macintosh) =============================================================== == System uname: 8.3.0 Power Macintosh powerpc macos-20041118 distcc 2.18.3-Apple powerpc-apple-darwin8.0 (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.4 [enabled] dev-lang/python: [Not Present] sys-apps/sandbox: [Not Present] sys-devel/autoconf: [Not Present] sys-devel/automake: [Not Present] sys-devel/binutils: [Not Present] sys-devel/libtool: [Not Present] virtual/os-headers: 7.1 ACCEPT_KEYWORDS="ppc-macos ~ppc-macos" AUTOCLEAN="yes" CBUILD="powerpc-apple-darwin8" CFLAGS="-O3 -pipe -mpowerpc-gfxopt -mstring -mmultiple -mcpu=750" CHOST="powerpc-apple-darwin8" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config /usr/ share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" CXXFLAGS="-O3 -pipe -mpowerpc-gfxopt -mstring -mmultiple -mcpu=750" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache collision-protect distlocks sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/ gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="ppc bash-completion bzip2 curl emboss expat libwww lua opengl png ppc-macos ssl unicode zlib userland_Darwin kernel_Darwin elibc_Darwin" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS, PORTDIR_OVERLAY
does this package have useflags? If so, could you report which ones you enabled and which you disabled (defaulted)?
(In reply to comment #2) > does this package have useflags? If so, could you report which ones you enabled > and which you disabled (defaulted)? vimcommander has no USE flags declared in the ebuild (i.e: IUSE="").
If it inherits from the vim eclass, we can't support it for the regular profiles. I can test this for collision- protect if that is the case -- just let me know.
Noone stops you from taking a look in the ebuild and keywording it if you feel like it works correctly. You don't need my permission for that, since you're a part of the ppc-macos arch team :)
I can't test any vim stuff for the regular profiles, as I have upgraded to vim7 via portage. I wanted to give you guys the opportunity to test and keyword for the regular profile before I looked at it for progressive and masked it for the regular profiles. :-)
Ah... then I misread your comment apparently. > I can test this for collision-protect ... This package defenitely doesn't work with the provided vim, since it wants to pull vim from portage. So j4rg0n, do your thing. Marking this bug as progressive target.
Created attachment 73754 [details, diff] BSD/Darwin Patch This package doesn't install cleanly on ppc-macos progressive as is due to the "chgrp root" command in the package "environment" file, which I'm guessing is some weird equivalent of a Makefile. I've cc-ed the BSD team and the package maintainer, as I am unfamiliar with this build system. Attached is a patch, but as the "environment" file keeps changing on me, I am unsure how to apply it.
I'd say to use chgrp 0, as we do for other ebuilds, so that we don't have to use different checks for BSD/GNU.
Eh?
Ciaranm, The "environment" file for this package uses "chgrp root", which doesn't work on BSD/Darwin because we don't have a "root" group. Is it possible to get this changed to "chgrp 0"? Thanks.
What environment file?
/var/tmp/portage/vimcommander-version/temp/environment
That's created by either Portage or ebuild.sh.
${PORTDIR}/eclass/vim-plugin.eclass:27 find ${S} -group 'portage' -exec chgrp root '{}' \; || die "chgrp failed" maybe that helps?
Ok, vim-plugin.eclass is probably now non-GNU safe, unless it isn't.
added in prefix
