[gentoo-user] about sys-fs/zfs-fuse and qmerge

[gentoo-user] about sys-fs/zfs-fuse and qmerge

[Harry Putnam]

I need a little coaching on qmerge usage.

I'm trying to emerge sys-fs/zfs-fuse.  The merge fails on a known bug,
a duplicate of another bug... 303623
  http://bugs.gentoo.org/show_bug.cgi?id=303623

In the comments... (#3) someone has asked to make the emerge once a
specific file is edited to remove Werror calls.

Someone replies with these few lines:
  ebuild /path/to/ebuild unpack
  edit the file
  ebuild /path/to/ebuild compile then install then qmerge

I did `ebuild unpack'
Found the file and made the necessary edits.

Then ebuild install.

But now looking a t man qmerge... its not at all clear how to install
this compiled package with qmerge

  qmerge <opts> <pkgnames>

Would pkgname be the binary `make' left in the build directory at:
  /var/tmp/portage/sys-fs/zfs-fuse-0.5.0/work/zfs-fuse-0.5.0

under:

 ls -F ./src/zfs-fuse/zfs-fuse:
 
    src/zfs-fuse/zfs-fuse*

so something like `qmerge  src/zfs-fuse/zfs-fuse*'
The man page does say its for intalling binaries.

I just don't want to make some mess thats hard to clean up and would
rather hear from someone who knows how to use `qmerge'.

Or even better some other work around.... The tail of the original
emerge failure is inlined below.  But its the exact output shown in
the bug referenced above.  And is the result of having Werror calls in
the CCFLAGS

There's even a patch from a previous duplicate bug its a simple edit
but then you have to go thru creating an edited ebuild and yatta
yatta.  
-------        ---------       ---=---       ---------      -------- 
tail of emerge -v sys-fs/zfs-fuse

[...]

>>> Compiling source in /var/tmp/portage/sys-fs/zfs-fuse-0.5.0/work/zfs-fuse-0.5.0/src ...
scons: Reading SConscript files ...
scons: done reading SConscript files.
scons: Building targets ...
gcc -o cmd/zdb/ptrace.o -c -pipe -Wall -Werror -std=c99 -Wno-switch -Wno-unused -Wno-missing-braces -Wno-parentheses -Wno-uninitialized -fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DTEXT_DOMAIN=\"zfs-fuse\" -DLINUX_AIO -ggdb -O2 -Ilib/libavl/include -Ilib/libnvpair/include -Ilib/libumem/include -Ilib/libzfscommon/include -Ilib/libzpool/include -Ilib/libsolcompat/include -Ilib/libzfs/include cmd/zdb/ptrace.c
gcc -o cmd/zdb/zdb.o -c -pipe -Wall -Werror -std=c99 -Wno-switch -Wno-unused -Wno-missing-braces -Wno-parentheses -Wno-uninitialized -fno-strict-aliasing -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_REENTRANT -DTEXT_DOMAIN=\"zfs-fuse\" -DLINUX_AIO -ggdb -O2 -Ilib/libavl/include -Ilib/libnvpair/include -Ilib/libumem/include -Ilib/libzfscommon/include -Ilib/libzpool/include -Ilib/libsolcompat/include -Ilib/libzfs/include cmd/zdb/zdb.c
cc1: warnings being treated as errors
cmd/zdb/zdb.c: In function 'zdb_dump_block_raw':
cmd/zdb/zdb.c:2007: error: ignoring return value of 'write', declared with attribute warn_unused_result
scons: *** [cmd/zdb/zdb.o] Error 1
scons: building terminated because of errors.
 * ERROR: sys-fs/zfs-fuse-0.5.0 failed:
 *   Make failed

[...]

Re: [gentoo-user] about sys-fs/zfs-fuse and qmerge

[William Kenworthy]

On Sun, 2010-03-14 at 00:43 -0600, Harry Putnam wrote:
> I need a little coaching on qmerge usage.
> 

qmerge is an argument to ebuild:

"ebuild file.ebuild compile install qmerge"

documented in "man ebuild"

BillK



-- 
William Kenworthy <billk@iinet.net.au>
Home in Perth!

Re: [gentoo-user] about sys-fs/zfs-fuse and qmerge

[Neil Bothwick]

[-- Attachment #1: Type: text/plain, Size: 993 bytes --]

On Sun, 14 Mar 2010 00:43:09 -0600, Harry Putnam wrote:

> In the comments... (#3) someone has asked to make the emerge once a
> specific file is edited to remove Werror calls.
> 
> Someone replies with these few lines:
>   ebuild /path/to/ebuild unpack
>   edit the file
>   ebuild /path/to/ebuild compile then install then qmerge
> 
> I did `ebuild unpack'
> Found the file and made the necessary edits.
> 
> Then ebuild install.
> 
> But now looking a t man qmerge... its not at all clear how to install
> this compiled package with qmerge
> 
>   qmerge <opts> <pkgnames>

It means ebuild compile, then ebuild install then ebuild qmerge. qmerge
is an action for ebuild, although there is an unreleated qmerge commands
in portage-utils.

Actually, you don't need all of this as ebuild will perform all
uncompleted previous stages, so you only need

ebuild unpack
edit file
ebuild qmerge


-- 
Neil Bothwick

I am in total control, but don't tell my wife.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[gentoo-user] Re: about sys-fs/zfs-fuse and qmerge

[Harry Putnam]

William Kenworthy <billk@iinet.net.au> writes:

[...]

> qmerge is an argument to ebuild:

Neil Bothwick <neil@digimed.co.uk> writes:

[...]

> Actually, you don't need all of this as ebuild will perform all
> uncompleted previous stages, so you only need
>
> ebuild unpack
> edit file
> ebuild qmerge

Nice... thanks... I got confused with the qmerge in portage utils.