Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug
Bug#: 86086
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: AMD64 Project <amd64@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Will Briggs <will.briggs@bigpond.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 86086 depends on: Show dependency tree
Bug 86086 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-03-20 19:24 0000
I wanted to emerge kdissert on my amd64 system.  There are no amd64 keywords
(stable or unstable) in the kdissert ebuild so I copied the kdissert part of
the portage tree to my my local portage overlay and added the keyword to the
ebuild (kdissert-0.3.6) (see additional info).

The emerge worked and some cursory testing seems to indicate that kdissert
operates correctly on this architecture.

Is there any reason why ~amd64 keyword cannot be added to the ebuild and
therefore have a wider testing on this platform amongs the user community?

Reproducible: Always
Steps to Reproduce:
1.Add ~amd64 keyword to ebuild in portage overlay
2.emerge kdissert

Actual Results:  
Kdissert emerges and seems to operate well

Expected Results:  
Kdissert emerges and seems to operate well

# Copyright 1999-2005 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/kde-misc/kdissert/kdissert-0.3.6.ebuild,v
1.1
2005/02/28 23:09:30 carlo Exp $

inherit kde

MY_P=${P/_/-}
S=${WORKDIR}/${MY_P}

DESCRIPTION="KDissert - a mindmapping-like tool"
HOMEPAGE="http://www.freehackers.org/~tnagy/kdissert/index.html"
#SRC_URI="http://www.freehackers.org/~tnagy/kdissert/${MY_P}.tar.bz2"
SRC_URI="http://www.kde-apps.org/content/files/12725-${MY_P}.tar.bz2"

SLOT="0"
LICENSE="GPL-2"
KEYWORDS="~x86 ~sparci ~amd64"
IUSE=""

DEPEND="dev-util/scons"
need-kde 3.2

# rotten Makefile stuff, can't use kde.eclass
src_compile() {
        ./configure --prefix="${D}/usr" --kdeincludes="$(kde-config
--prefix)/include"  || configure failed
        emake || emake failed
}

src_install() {
        einstall || einstall failed
}

------- Comment #1 From Chris White (RETIRED) 2005-03-21 00:24:57 0000 -------
~amd64 marking request for kdissert.

amd64 re-assignment
kde herd cc'ed so they're aware of the marking request.

------- Comment #2 From Marcus D. Hanwell 2005-03-21 00:51:51 0000 -------
Please see
http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=2 for
details on filing keyword bugs, there is no need to include ebuilds etc, but
the ebuild category and version does help.

I have tested this and marked it ~amd64 - kde-misc/kdissert-0.3.6

Bug List: (This bug is not in your last search results)   Show last search results      Search page      Enter new bug