[gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-libs/confuse: confuse-2.7.ebuild ChangeLog
On 1 March 2013 08:16, Mike Frysinger (vapier) vap...@gentoo.org wrote: vapier 13/03/01 08:16:02 Modified: confuse-2.7.ebuild ChangeLog Log: Add arm lovin. (Portage version: 2.2.0_alpha163/cvs/Linux x86_64, signed Manifest commit with key FB7C4156) Revision ChangesPath 1.13 dev-libs/confuse/confuse-2.7.ebuild file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/confuse/confuse-2.7.ebuild?rev=1.13view=markup plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/confuse/confuse-2.7.ebuild?rev=1.13content-type=text/plain diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/dev-libs/confuse/confuse-2.7.ebuild?r1=1.12r2=1.13 Index: confuse-2.7.ebuild === RCS file: /var/cvsroot/gentoo-x86/dev-libs/confuse/confuse-2.7.ebuild,v retrieving revision 1.12 retrieving revision 1.13 diff -u -r1.12 -r1.13 --- confuse-2.7.ebuild 30 Oct 2012 11:18:49 - 1.12 +++ confuse-2.7.ebuild 1 Mar 2013 08:16:02 - 1.13 @@ -1,6 +1,6 @@ -# Copyright 1999-2012 Gentoo Foundation +# Copyright 1999-2013 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 -# $Header: /var/cvsroot/gentoo-x86/dev-libs/confuse/confuse-2.7.ebuild,v 1.12 2012/10/30 11:18:49 blueness Exp $ +# $Header: /var/cvsroot/gentoo-x86/dev-libs/confuse/confuse-2.7.ebuild,v 1.13 2013/03/01 08:16:02 vapier Exp $ EAPI=3 @@ -10,7 +10,7 @@ LICENSE=ISC SLOT=0 -KEYWORDS=alpha amd64 hppa ia64 ~mips ppc ppc64 sparc x86 ~sparc-fbsd ~x86-fbsd ~x86-interix ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~x86-solaris +KEYWORDS=alpha amd64 arm hppa ia64 ~mips ppc ppc64 sparc x86 ~sparc-fbsd ~x86-fbsd ~x86-interix ~amd64-linux ~x86-linux ~ppc-macos ~x86-macos ~x86-solaris IUSE=nls static-libs DEPEND=sys-devel/flex straight to stable? Not even keeping it to testing just for a week or so? -- Regards, Markos Chandras - Gentoo Linux Developer http://dev.gentoo.org/~hwoarang
Re: [gentoo-dev] New eclass: autotools-multilib-minimal
On 02/28/2013 09:30 AM, Michał Górny wrote:
Setting that variable would invalidate metadata cache.
different approach attached
--- eclass/multilib-minimal.eclass
+++ eclass/multilib-minimal.eclass
@@ -18,12 +18,6 @@
#
# If you need generic install rules, use multilib_src_install_all function.
-# @ECLASS-VARIABLE: DISABLE_MULTILIB
-# @DESCRIPTION:
-# set to ON to disable multilib entirely
-# this is not meant to be set in the ebuild
-: ${DISABLE_MULTILIB:=OFF}
-
# EAPI=5 is required for meaningful MULTILIB_USEDEP.
case ${EAPI:-0} in
@@ -31,22 +25,28 @@
*) die EAPI=${EAPI} is not supported ;;
esac
-_multilib_inherit=
-if [[ ${DISABLE_MULTILIB} == OFF ]] ; then
- _multilib_inherit=multilib-build
-fi
-inherit ${_multilib_inherit}
+inherit multilib-build
EXPORT_FUNCTIONS src_configure src_compile src_test src_install
+
+unset DISABLE_MULTILIB
+_multilib-minimal_set_globals() {
+ if [[ $(multilib_get_enabled_abis) == ${DEFAULT_ABI} ]] ; then
+ DISABLE_MULTILIB=ON
+ fi
+}
+_multilib-minimal_set_globals
+
+
multilib_copy_sources() {
_abi_copy_sources() {
einfo ${ABI}: copying to ${BUILD_DIR}
cp -pR ${S} ${BUILD_DIR} || die failed to copy sources
}
- if [[ ${DISABLE_MULTILIB} == OFF ]] ; then
+ if [[ -z ${DISABLE_MULTILIB} ]] ; then
einfo Will copy sources to abi-specific dirs
multilib_foreach_abi _abi_copy_sources
fi
@@ -70,7 +70,7 @@
popd /dev/null || die
}
- if [[ ${DISABLE_MULTILIB} == OFF ]] ; then
+ if [[ -z ${DISABLE_MULTILIB} ]] ; then
multilib_foreach_abi _abi_src_configure
else
_common_src_configure
@@ -94,7 +94,7 @@
popd /dev/null || die
}
- if [[ ${DISABLE_MULTILIB} == OFF ]] ; then
+ if [[ -z ${DISABLE_MULTILIB} ]] ; then
multilib_foreach_abi _abi_src_compile
else
_common_src_compile
@@ -118,7 +118,7 @@
popd /dev/null || die
}
- if [[ ${DISABLE_MULTILIB} == OFF ]] ; then
+ if [[ -z ${DISABLE_MULTILIB} ]] ; then
multilib_foreach_abi _abi_src_test
else
_common_src_test
@@ -143,7 +143,7 @@
popd /dev/null || die
}
- if [[ ${DISABLE_MULTILIB} == OFF ]] ; then
+ if [[ -z ${DISABLE_MULTILIB} ]] ; then
multilib_foreach_abi _abi_src_install
else
_common_src_install
[gentoo-dev] The Gentoo Qt Project wants your help!
The Gentoo Qt Project wants your help! == The Gentoo Qt Project is a small team responsible for maintaining the Qt libraries and associated applications within our beloved distro. Over time the number of packages we maintain has grown. Not only is there quite some work to be done to get the shiny new Qt5 version ready for the portage tree, we now also have our own light-weight Qt-based desktop environment in Razor-qt, as well as a growing number of Qt-based applications. Recently a few of our team members have left to do other things, so we are looking for new people to help us out! Whatever your skill level, there is probably something you can do to help! We specifically are looking for people to help us to do the following: 1. Get Qt5 ready for inclusion in the tree. This includes writing and improving ebuilds and eclasses, testing to build those, filing bug reports on failure, finding fixes for those bugs, reporting problems upstream. We do development in the qt overlay, using git. 2. Application maintenance. At the moment we simply don't have the manpower to actively maintain all Qt-based applications that we have an interest in. A number of those could use a more dedicated maintainer. This can be either a Gentoo developer or a proxy-maintainer. You would be responsible for spotting version bumps, updating ebuilds, handling bug reports and contacting upstream developers where necessary. An overview of the packages we (co-)maintain is here: http://euscan.iksaif.net/herds/qt/ For a specific list of packages we could use help with, see below. 3. Bug handling. See http://tiny.cc/qtbugs for our open bugs. We can use help to test and confirm bugs and proposed patches; to see if bugs are filed upstream and if there are patches available; to keep an eye on bug-fix releases. 4. Documentation. We would like to see more user guides, and updates to our FAQ, on the Gentoo Wiki. What we can give you is a friendly developer team, with members spread all over the world; assistance with ebuild writing skills; commit access to a lively git-based overlay, even if you are not a developer; mentoring in case you do want to become a developer; a dedicated #gentoo-qt IRC channel; and the satisfaction that you help improving Gentoo, the distro we all love. You can contact us on q...@gentoo.org, or the #gentoo-qt IRC channel. == New primary maintainer needed: == app-admin/keepassx app-cdr/acetoneiso app-editors/focuswriter app-editors/tea app-editors/znotes dev-python/pyside and related packages dev-util/beediff dev-util/eggy dev-util/monkeystudio media-sound/mp3diags media-video/avidemux (bundled libs) media-video/qx11grab net-im/psi (urgently needs to be updated to new release version) net-libs/qmf (needs gcc-4.7 fix) x11-misc/qtfm == We could also use a hand with: == app-text/goldendict dev-games/tiled dev-util/xxdiff media-gfx/nomacs media-sound/coquillo net-news/quiterss net-news/rssguard www-client/qupzilla x11-misc/basqet app-editors/qwriter app-editors/qxmledit app-emulation/qtemu app-mobilephone/past app-mobilephone/qtadb app-office/qchartdiary app-text/cb2bib dev-db/dbmodel dev-db/sqliteman dev-libs/qjson dev-libs/qoauth dev-tex/qtexengine dev-tex/texamator dev-util/qfsm dev-util/universalindentgui dev-vcs/hgview dev-vcs/qct dev-vcs/qsvn media-gfx/pencil media-gfx/pictureflow media-gfx/qosmic media-gfx/qvv net-analyzer/nmapsi net-ftp/oneclickftp net-ftp/qshare net-ftp/scythia net-im/qwit net-misc/dnetstats net-misc/netfleet sci-calculators/qalculator sci-visualization/kst x11-misc/okindd x11-misc/qps x11-misc/qsynergy x11-misc/tinymount -- Cheers, Ben | yngwin Gentoo developer Gentoo Qt project lead, Gentoo Wiki admin
Re: [gentoo-dev] The Gentoo Qt Project wants your help!
On 02/03/2013 07:54, Ben de Groot wrote: 1. Get Qt5 ready for inclusion in the tree. This includes writing and improving ebuilds and eclasses, testing to build those, filing bug reports on failure, finding fixes for those bugs, reporting problems upstream. We do development in the qt overlay, using git. If you decide to work on Qt5, my suggestion if for somebody to proxy it on main tree *under package.mask* and shoot me an email. Leveraging the tinderbox will at least allow you to find failure points. Good luck, -- Diego Elio Pettenò — Flameeyes flamee...@flameeyes.eu — http://blog.flameeyes.eu/
