Summary: | sys-fs/zfs-fuse-9999 live ebuild | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michal Janke <m.yankee> |
Component: | Current packages | Assignee: | Christian Parpart (RETIRED) <trapni> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | bug, larstobi |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
updated patch
The ebuild, as pasted in the description. updated ebuild updated patch file rc script with questionable sleep call |
Description
Michal Janke
2009-09-09 22:35:35 UTC
Created attachment 203649 [details]
updated patch
Replace the file in $PORTDIR/sys-fs/zfs-fuse/files/9999/ with this one and (re-)digest the ebuild.
I guess that at first you didn't notice the attachment form, which is why the ebuild is pasted inline rather than attached like the patch... Anyways, thanks for submitting your updates! Assigning to maintainer. (In reply to comment #0) > zfs-fuse development team has recently moved their sources to git. The old > SRC_URI is no longer valid. > Also, there are some manpages available now. Here's a proposed ebuild update. > One of the patches needed an update as well. Many thanks for this notification. I always have felt sad about not having man-pages for zfs though. Created attachment 203847 [details] The ebuild, as pasted in the description. (In reply to comment #2) > I guess that at first you didn't notice the attachment form, which is why the > ebuild is pasted inline rather than attached like the patch... The thing is, I still don't see it while starting a new bug report. I knew about it, but somehow it seemed reasonable to me that the ebuild should be contained within the main desription, not as an attachment to a comment. This might just be stupid of me :) Anyway, I've added it as an attachment as well now for convenience. Could someone show an interest in this? The old ebuild is BROKEN because of the repo change! If it is of interest for inclusion, I've successfully compiled a ~sparc version with some modifications. The submitted diff patch for ztest.c is slightly off due to recent revisions in the git repository. The ebuild has been modified to include reference to the current zfs-fuse development site. Also, the rc script seemed to have problems attempting a mount immediately following a start of the fuse daemon without any pools. I added "sleep 3" prior to the call to mount which seemed to work. As an aside, for sparc, I also keyworded both app-emulation/fuse-utils and app-emulation/libspectrum by adding the ~sparc keyword (in local ebuilds as ~sparc was not an accepted keyword in those - I suppose these should be submitted as enhancement requests under those packages). Created attachment 224623 [details]
updated ebuild
Created attachment 224625 [details, diff]
updated patch file
Created attachment 224627 [details]
rc script with questionable sleep call
(In reply to comment #6) > As an aside, for sparc, I also keyworded both app-emulation/fuse-utils and completely different project for the fuse-utils libraries. sorry for the noise. saw the requirements on http://gitorious.org/zfs-fuse/zfs-fuse/blobs/master/INSTALL for fuse-utils and had installed fuse-utils after successful install of zfs-fuse. app-emulator/fuse-utils should not have been mentioned. Maybe we could create ebuild which joins advantages of your ebuild and fixes from mine? In bug #332395 i've uploaded live ebuild, which has fixed some issues on hardened platform (but not all, i got "smashing stack attack" while i use zdb). Closing since zfs-fuse was removed from tree. No need to have 2 bugs for "New package". *** This bug has been marked as a duplicate of bug 358697 *** |