Os-portable archiver (Windows, Linux). Features archive volume spanning, compression, authenticated encryption. Supports 7Z, 7-Zip sfx, ARJ, BZip2, CAB, CHM, CPIO, DEB, GZip, ISO, JAR, LHA, LZH, NSIS, OOo, PAQ, PEA, QUAD, RAR, RPM, split, TAR, Z, ZIP. I know some people who use it, and upstream is active. I wrote an ebuild, will attach it in a moment. Unfortunately, the program is written in Pascal and it would be difficult to compile manually, so this is a binary distribution, and works only on x86 and amd64. I tested it on amd64 stable system, but it should also work on x86.
Created attachment 119422 [details] peazip-1.7.ebuild This is the proposed ebuild. For category I suggest app-arch.
Bumped to version 1.8 http://www.kde-apps.org/content/show.php/PeaZip?content=52805
hello? why isn't this on portage?
Created attachment 127462 [details] peazip-1.8.2.ebuild
Created attachment 128025 [details] Peazip 1.9 Bump to version 1.9
Why do you all bump the whole ebuild, if the changes you make are only minor (one-two lines)? It just makes the attachments section more cluttered, and may make it harder for devs to see a clear image... more noise does not mean more success.
1.9 ebuild appears to work (so far) for 2.2, with just renaming it
Created attachment 171184 [details] peazip-2.3a.ebuild
Comment on attachment 171184 [details] peazip-2.3a.ebuild 1.9 renamed works with 2.3a (latest version)
src_compile() { true # no compilation required, it's binary package } Wuut? With all due respect and not to overly criticize the people who wrote the ebuild, but... "It's a binary package"? I wish to remind everyone that this is Gentoo and the application in question is Open Source...
well, you're right, but after a quick look at the sources i understood the reason why... from readme.txt -------------------------- To compile sources you need Lazarus IDE (https://sourceforge.net/projects/lazarus). Open .lpi project files and do "build all" to compile the executables. Please read the following documentation to understand what is contained in the source package and please see precompiled program's packages to know what third parts executables (7z, arc, paq...) are needed by PeaZip. -- Seems that the code can be compiled with the free pascal compiler, but we need a build tool to (hopefully) bypass the ide... in fact that's why we have make, cmake, automake, autotools... etc...
(this is an automated message based on filtering criteria that matched this bug) 'EBUILD' is in the KEYWORDS which should mean that there is a ebuild attached to this bug. This bug is assigned to maintainer-wanted which means that it is not in the main tree. Heuristics show that no Gentoo developer has commented on your ebuild. Hello, The Gentoo Team would like to firstly thank you for your ebuild submission. We also apologize for not being able to accommodate you in a timely manner. There are simply too many new packages. Allow me to use this opportunity to introduce you to Gentoo Sunrise. The sunrise overlay[1] is a overlay for Gentoo which we allow trusted users to commit to and all users can have ebuilds reviewed by Gentoo devs for entry into the overlay. So, the sunrise team is suggesting that you look into this and submit your ebuild to the overlay where even *you* can commit to. =) Because this is a mass message, we are also asking you to be patient with us. We anticipate a large number of requests in a short time. Thanks, On behalf of the Gentoo Sunrise Team, Jeremy. [1]: http://www.gentoo.org/proj/en/sunrise/ [2]: http://overlays.gentoo.org/proj/sunrise/wiki/SunriseFaq
I would really like to see peazip in the portage tree again. Is there some progress on this yet?
Yes, at least the binaries if it cant be compiled by portage.
Version 3.0 is out. Perhaps (?) might be worth having peazip* and peazip-bin ebuilds so the distinction will be obvious to the user. *when it can be determined whether PeaZip can be compiled w/o an IDE. Would be interested in using PeaZip even if only in Sunrise.
Could lazbuild be used to build PeaZip from the command line? From the Lazarus FAQ @ http://wiki.lazarus.freepascal.org/Lazarus_Faq : "If you can't use the IDE to build your applications, use lazbuild. This is a command line version of the IDE to build lazarus projects and packages."
http://peazip.sourceforge.net/changelog.html 3.1 is out # 2010 04 29 * 3.1 o BACKEND + (Windows) 7z 9.13 beta o FILE MANAGER + Added entries to add and organize bookmarks in navigation bar + Options > Settings: click ok to accept changes or cancel to discard + Various minor updates + (Linux) Added service menus for KDE4/Dolphin o EXTRACTION and ARCHIVING + Fixed: removed unsupported -mmt switch for creation of GZip archives + Last used custom application for archiving and extraction is automatically remembered + Ok and Cancel buttons can now be selected using tab in archiving and extraction interfaces, and Ok button is now automatically selected to allow confirm job simply pressing enter + In extraction/archiving interfaces click Ok to apply the changes to options and launch the job (or only to apply changes if the layout is empty), click Cancel to discard the changes and the job
Any more votes?
(In reply to comment #18) Yes
(In reply to comment #18) > Any more votes? > yes
> Any more votes? Aye.
Peazip is up to 3.6.1 now. I'd love for this program to enter the Portage tree or an overlay... Possibly even with the addition of wrappers to use system backends for the compressors should they be available
I'll make an ebuild...
Oh, sorry if I sounded bossy, that was not my intention. :(
No really... I'm not kidding. A temporary build, it's a just a binary package, so ebuild will be easy to make. BTW why don't you try file-roller or ark etc... ?
Am not sure, but maybe because of the heavy dependencies. I'm running an lxde system here, so I try to emerge as few as possible gnome stuff (like no gvfs etc) and keep away from qt/kde completely. In the end, peazip can (un)compress (some) paq archives ... at least in my case that's the interesting thing about it.
You should try xarchiver. Attaching the ebuild in a while....
Created attachment 262973 [details] Latest ebuild for now. I've tested this only on AMD64. Dependencies are missing for x86. So please... if someone is running an x86 system report the output of ldd /usr/bin/peazip.
Why do I use Peazip? It's the best program out there! All the other I tried either are very buggy or lack the most basic features. Peazip comes closest to a full archiver tool (like 7z on Windows) Thanks a lot for the ebuild! It works just fine, but has a few shortcomings: /var/tmp/portage/app-arch/peazip-3.6.1/temp/environment: line 216: !gtk: command not found /var/tmp/portage/app-arch/peazip-3.6.1/temp/environment: line 219: qt: command not found ^ when installing the ebuild - it puts peazip into /user/local and /opt instead of /usr - no menu icon created (Xfce here) - some kind of wrapper/symlink to use the system compressor backends (when available) would be cool. I might consider making that myself, even. Hang on. again, thanks!
Created attachment 262977 [details] output of ldd /usr/local/bin/peazip (x86) Thank you for the ebuild. Good work. Attached is the ldd output as requested. I have emerged it with USE="-qt gtk kde"
Created attachment 262981 [details] output of ldd /usr/local/bin/peazip (x86) qt version Here is the ldd from when I installed with USE="-gtk qt kde" The window decorations where not quite right. The close (X) button was missing.
Created attachment 262983 [details] tidied up I tidied the ebuild up a bit and fixed the bug with the use flags. The other bugs remain; I have only very limited knowledge about making ebuilds. The menu entry should appear once it is modified to move peazip to its proper place in /usr, not /usr/local. :)
Created attachment 262985 [details] minor fix (whoops)
(In reply to comment #29) > Why do I use Peazip? It's the best program out there! All the other I tried > either are very buggy or lack the most basic features. Peazip comes closest to > a full archiver tool (like 7z on Windows) > > Thanks a lot for the ebuild! It works just fine, but has a few shortcomings: > > /var/tmp/portage/app-arch/peazip-3.6.1/temp/environment: line 216: !gtk: > command not found > /var/tmp/portage/app-arch/peazip-3.6.1/temp/environment: line 219: qt: command > not found > ^ when installing the ebuild > Yeah, I dont know why it rejects the !<use> comment. Will ask in teh forum. > - it puts peazip into /user/local and /opt instead of /usr > - no menu icon created (Xfce here) It downloads the tbz archive that the peazip team provided (I don't know the consequence of manipulating them, I'm not a dev), so they decide where to put stuff, including the DE integration. I'm on KDE so I'll try it out. > - some kind of wrapper/symlink to use the system compressor backends (when > available) would be cool. I might consider making that myself, even. Hang on. > Hu? peazip can use backends like that?.. I didn't know... > again, thanks! > (In reply to comment #30) > Created an attachment (id=262977) [details] > output of ldd /usr/local/bin/peazip (x86) > > Thank you for the ebuild. > Good work. > Attached is the ldd output as requested. > I have emerged it with USE="-qt gtk kde" > Also post the output of - equery belongs /usr/lib/libX11.so.6 /usr/lib/libgdk_pixbuf-2.0.so.0 /usr/lib/libgtk-x11-2.0.so.0 /usr/lib/libgdk-x11-2.0.so.0 /usr/lib/libgobject-2.0.so.0 /usr/lib/libglib-2.0.so.0 /usr/lib/libgthread-2.0.so.0 /usr/lib/libgmodule-2.0.so.0 /usr/lib/libpango-1.0.so.0 /lib/libpthread.so.0 /usr/lib/libatk-1.0.so.0 /lib/libdl.so.2 /lib/libc.so.6 /usr/lib/libxcb.so.1 /usr/lib/libgio-2.0.so.0 /lib/libresolv.so.2 /lib/libz.so.1 /lib/librt.so.1 /lib/libm.so.6 /usr/lib/libpangocairo-1.0.so.0 /usr/lib/libXfixes.so.3 /usr/lib/libcairo.so.2 /usr/lib/libpangoft2-1.0.so.0 /usr/lib/libfontconfig.so.1 /usr/lib/libXi.so.6 /usr/lib/libXrandr.so.2 /usr/lib/libXext.so.6 /usr/lib/libXcursor.so.1 /usr/lib/libXcomposite.so.1 /usr/lib/libXdamage.so.1 /usr/lib/libXrender.so.1 /usr/lib/libXau.so.6 /usr/lib/libXdmcp.so.6 /usr/lib/libpixman-1.so.0 /usr/lib/libpng14.so.14 /usr/lib/libfreetype.so.6 /usr/lib/libexpat.so.1 /usr/lib/libEGL.so.1 /usr/lib/qt4/libQtGui.so.4 /usr/lib/qt4/libQtCore.so.4 /usr/lib/libxcb-shm.so.0 /usr/lib/libxcb-render.so.0 //usr/lib/opengl/nvidia/lib/libGL.so.1 /usr/lib/gcc/i686-pc-linux-gnu/4.4.5/libgcc_s.so.1 /usr/lib/libSM.so.6 /usr/lib/libICE.so.6 /usr/lib/gcc/i686-pc-linux-gnu/4.4.5/libstdc++.so.6 //usr/lib/opengl/nvidia/lib/libnvidia-tls.so.260.19.36 /usr/lib/libnvidia-glcore.so.260.19.36 /lib/libuuid.so.1 (In reply to comment #31) > Created an attachment (id=262981) [details] > output of ldd /usr/local/bin/peazip (x86) qt version > > Here is the ldd from when I installed with USE="-gtk qt kde" > > The window decorations where not quite right. > The close (X) button was missing. > Here post the output of - equery belongs /usr/local/lib/libqt4intf.so /lib/libc.so.6 /usr/lib/qt4/libQtCore.so.4 /usr/lib/qt4/libQtGui.so.4 /usr/lib/gcc/i686-pc-linux-gnu/4.4.5/libstdc++.so.6 /lib/libm.so.6 /usr/lib/gcc/i686-pc-linux-gnu/4.4.5/libgcc_s.so.1 /usr/lib/libgthread-2.0.so.0 /lib/librt.so.1 /usr/lib/libglib-2.0.so.0 /lib/libpthread.so.0 /lib/libz.so.1 /lib/libdl.so.2 /usr/lib/libpng14.so.14 /usr/lib/libfreetype.so.6 /usr/lib/libSM.so.6 /usr/lib/libICE.so.6 /usr/lib/libXrender.so.1 /usr/lib/libXrandr.so.2 /usr/lib/libfontconfig.so.1 /usr/lib/libXext.so.6 /usr/lib/libX11.so.6 /lib/libuuid.so.1 /usr/lib/libxcb.so.1 /usr/lib/libXau.so.6 /usr/lib/libXdmcp.so.6 /usr/lib/libexpat.so.1 Yeah the close button is missing, I think it's an upstream issue. (In reply to comment #33) > Created an attachment (id=262985) [details] > minor fix (whoops) > This ebuild is bound to break on amd64 systems (when you don't have the right dependencies preinstalled). BTW I don't understand what this ebuild fixes. Are you on x86?
(In reply to comment #34) > Yeah the close button is missing, I think it's an upstream issue. It is no big deal since the gtk version works fine. Output of equery b as requested (duplicates removed) ---------------------------- with USE="gtk -qt kde": ---------------------------- dev-libs/atk-1.33.6 dev-libs/expat-2.0.1-r3 dev-libs/glib-2.28.0 media-libs/fontconfig-2.8.0-r1 media-libs/freetype-2.4.4 media-libs/libpng-1.4.5 media-libs/mesa-7.10-r1 sys-apps/util-linux-2.19 sys-devel/gcc-4.4.5 sys-libs/glibc-2.12.2 sys-libs/zlib-1.2.5-r2 x11-drivers/nvidia-drivers-260.19.36 x11-libs/cairo-1.10.2-r1 x11-libs/gdk-pixbuf-2.23.0 x11-libs/gtk+-2.24.0 x11-libs/libICE-1.0.7 x11-libs/libSM-1.2.0 x11-libs/libX11-1.4.1 x11-libs/libXau-1.0.6 x11-libs/libXcomposite-0.4.3 x11-libs/libXcursor-1.1.11 x11-libs/libXdamage-1.1.3 x11-libs/libXdmcp-1.1.0 x11-libs/libXext-1.2.0 x11-libs/libXfixes-4.0.5 x11-libs/libXi-1.4.1 x11-libs/libXrandr-1.3.1 x11-libs/libXrender-0.9.6 x11-libs/libxcb-1.7 x11-libs/pango-1.28.3 x11-libs/pixman-0.20.2 x11-libs/qt-core-4.7.1-r1 x11-libs/qt-gui-4.7.1-r1 ----------------------------- with USE="qt -gtk kde" ----------------------------- dev-libs/expat-2.0.1-r3 dev-libs/glib-2.28.0 media-libs/fontconfig-2.8.0-r1 media-libs/freetype-2.4.4 media-libs/libpng-1.4.5 sys-apps/util-linux-2.19 sys-devel/gcc-4.4.5 sys-libs/glibc-2.12.2 sys-libs/zlib-1.2.5-r2 x11-libs/libICE-1.0.7 x11-libs/libSM-1.2.0 x11-libs/libX11-1.4.1 x11-libs/libXau-1.0.6 x11-libs/libXdmcp-1.1.0 x11-libs/libXext-1.2.0 x11-libs/libXrandr-1.3.1 x11-libs/libXrender-0.9.6 x11-libs/libxcb-1.7 x11-libs/qt-core-4.7.1-r1 x11-libs/qt-gui-4.7.1-r1
> Yeah, I dont know why it rejects the !<use> comment. Will ask in teh forum. I do. That's what my fixed ebuild is for ;) > It downloads the tbz archive that the peazip team provided (I don't know the > consequence of manipulating them, I'm not a dev), so they decide where to put > stuff, including the DE integration. Yes, but it's not the proper place for stuff installed from a package. The archive assumes it was installed manually. Packages should always go into /usr, or in our case (since it's a binary package) into /opt. Putting it into /usr should fix the missing menu entry though, so I say we should put it there. > Hu? peazip can use backends like that?.. I didn't know... Of course! :) Peazip is just a graphical frontend to all the packers. The proper Gentoo way to handle the backends is to strip them out of the install, replace them with symlinks to the system backends and add the needed dependencies for the system backends to the ebuild. btw, are the x86 emul libs for opengl really needed?? What does Peazip have to do with 3D rendering?
(In reply to comment #36) > > Yeah, I dont know why it rejects the !<use> comment. Will ask in teh forum. > > I do. That's what my fixed ebuild is for ;) > > > It downloads the tbz archive that the peazip team provided (I don't know the > > consequence of manipulating them, I'm not a dev), so they decide where to put > > stuff, including the DE integration. > > Yes, but it's not the proper place for stuff installed from a package. The > archive assumes it was installed manually. Packages should always go into /usr, > or in our case (since it's a binary package) into /opt. Putting it into /usr > should fix the missing menu entry though, so I say we should put it there. > > > Hu? peazip can use backends like that?.. I didn't know... > > Of course! :) Peazip is just a graphical frontend to all the packers. > The proper Gentoo way to handle the backends is to strip them out of the > install, replace them with symlinks to the system backends and add the needed > dependencies for the system backends to the ebuild. > > btw, are the x86 emul libs for opengl really needed?? What does Peazip have to > do with 3D rendering? > Yeah, the ldd output stated the libraries are required.
Created attachment 263123 [details] Dependency problems with x86 resolved @haarp Also about the "!qt" and !gtk etc... notices, they don't appear in my case, you should be running a stable portage version.
Created attachment 264353 [details] Update ebuild. You all might not have noticed but the peazip site runs on Microsoft IIS 6.
Created attachment 265163 [details] Corrected ebuild for 3.6.2 This also fixes some other issues: Now supports gnome use flag. Installs to /opt (that's where binary pkgs belong, AFAIK) The links are also correct now. NOT tested under gnome or kde, I am on e17, so see for yourself whether the integration works. I have a problem however: The filebrowser freezes and I have to kill peazip. The installation however seems clean now, as all the other ebuilds posted did not work with 3.6.2 at all... Please report if the filebrowser works for you (and why ;-> )
there is 4.0 version on their website
I use PeaZip in Gentoo, and would like to see an ebuild in the main Portage tree, even if it is just an ebuild for the binary package. In addition to the source package and binary package, PeaZip also has another binary version named 'PeaZip Portable', which does not require installation, just unpacking, creation of a symlink and the copying of three files. See https://fitzcarraldoblog.wordpress.com/2015/05/03/installing-peazip-in-gentoo-linux/ for the steps I used to do that in Gentoo. Perhaps someone could write an ebuild ('app-arch/peazip-portable-bin'?) to merge PeaZip Portable in Gentoo, which presumably would be somewhat easier than an ebuild for the standard PeaZip binary package.
PeaZip for Linux 5.7.2 http://www.peazip.org/peazip-linux.html Code: https://github.com/giorgiotani/PeaZip/
Actually the code is (strangely) here in the zip: https://github.com/giorgiotani/PeaZip/releases
