make rpm support optional?
being I'm on a gentoo system atm I do not have rpm installed.
Also you might wanna add a check in the configure script for it :)
my compile error :(
In file included from main.cpp:22:
kpackwizardclass.h:41:24: rpm/rpmlib.h: No such file or directory
kpackwizardclass.h:42:24: rpm/header.h: No such file or directory
Hey,
This is a bug, I wanted to use RPMLIB but due to compatibility with non-rpm systems I am using command-line version but I've forgot to remove those headers.
Download KPack 0.1.4-2 or remove
#include <rpm/rpmlib.h>
#include <rpm/header.h>
from src/kpackwizardclass.h and src/SingleRPMInstaller.cpp.
really nice start however I have no idea what commands are being ran, where it's being installed etc.
I just tried to install a source code package as a normal user and got no error message of any kind just said it installed, which I know to be not true.
when as a normal user it should prompt for root in order to install.
Running kpack also generates nothing no dialog, no output on the command line.
There's no error handling in this version.
The command being run:
- mkdir /tmp/kpack-install
- cp [filename] /tmp/kpack-install
- tar -xfz OR -xfj [filename.tar.bz2/filename.tar.gz]
- cd [source directory]
- ./configure
- make -n [for progressbar]
- make
- kdesu --noignorebutton -d --caption Kpack -c "make install"
Without error handling, KPack cannot tell you you have no KDESU installed. I can implement my own dialog, but if I use KDESU KPack will look more integrated into KDE. I will fix it in future versions, and implement KDESU dialog AND KPack's own root dialog.
any slackware .tgz package contains binaries and libraries (including devel).
1. it is a tar.gz file
2. to install -> tar -zxvf -C / (root)
3. there's a folder "/install" which contains a script file "doinst.sh" which creates symbolic links and removes when uninstalled.
if we extract the slackware packages on '/' (root) then it is like installing. and executing the /install/doinst.sh will create symbolic links etc., required.
To remove, just delete the files which are present in the tgz files in the filesystem and remove the symbolic links which are present in doinst.sh file.
that's it.
A package manager that handles both RPM and DEB packages as well as stuff built from source is a much needed application.
However, one of the major things which it needs to do is to track dependencies.
For example:
I install an RPM and it has unresolved dependencies on some libraries. The package manager needs to check and see if I actually have these libraries installed and if so, go ahead and install the RPM.
I have a library that I built from source and I want to know which other stuff depends on it. The package manager should be able to tell me this by building a data base from the ld.so.cache.
cze
wlasnie sciagam twoj instalator.
mam pytanie. Czy bedzieon mial/ ma mozliwosc instalowania programu z mozliwoscia zmieniania lokacji i dowiazywanie dynamicznych bibliotek( cos jak w pcbsd0 A TAK SWOJA DROGA TO BARDZO DOBRY POMYSL.
DZIEKI
However installation without dependencies is not so useful.
Also, could the distributor create some more complex install package, e.g. to display some instructional text?
It would be a good idea to use Smart Package Manager as backend - it already supports a variety of package formats and is able to handle dependencies.
great job sabby,
for the moment i'm just getting a four zero four instead of the tarball, but i've got a question for you?
is KPack some kind of KPackage (dist. pm. front end) or is it able to create executable installers (like BitRock ~http://www.bitrock.com~ or like win32 installers)
anyway great job and hope the download link will get corrected
Damn, thanks! I didn't know download link was broken... KPack is flexible so I can implement any type of install. In next version automatic compiling (in future QMake projects too) will be supported with progressbar.
RPM Dependency check, source installing improved, output console
Ratings & Comments
18 Comments
When I tried to make KPack 0.1.4-2 on Fedora Core 5, here's the output:
Making all in src make[2]: Entering directory `/mnt/Common/Downloads/Linux/kpack-0.1.4-2/src' /usr/lib/qt-3.3/bin/uic -L /usr/lib/kde3/plugins/designer -nounload -o KPackWizardDialog.h ./KPackWizardDialog.ui /usr/lib/qt-3.3/bin/uic -L /usr/lib/kde3/plugins/designer -nounload -o KPackMaker.h ./KPackMaker.ui source='main.cpp' object='main.o' libtool=no \ depfile='.deps/main.Po' tmpdepfile='.deps/main.TPo' \ depmode=gcc3 /bin/sh ../admin/depcomp \ g++ -DHAVE_CONFIG_H -I. -I. -I.. -I/usr/include/kde -I/usr/lib/qt-3.3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -Wnon-virtual-dtor -Wno-long-long -Wundef -Wall -W -Wpointer-arith -Wwrite-strings -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -O2 -Wformat-security -Wmissing-format-attribute -fno-exceptions -fno-check-new -fno-common -c -o main.o `test -f 'main.cpp' || echo './'`main.cpp main.cpp: In function ‘int main(int, char**)’: main.cpp:75: error: ‘KPackMaker’ was not declared in this scope main.cpp:75: error: ‘maker’ was not declared in this scope main.cpp:75: error: expected type-specifier before ‘KPackMaker’ main.cpp:75: error: expected `;' before ‘KPackMaker’ make[2]: *** [main.o] Error 1 make[2]: Leaving directory `/mnt/Common/Downloads/Linux/kpack-0.1.4-2/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/mnt/Common/Downloads/Linux/kpack-0.1.4-2' make: *** [all] Error 2 [chris@dhcppc0 kpack-0.1.4-2]$
How can I fix this problem?hi it should be great if you'll include the deb support with checkinstall.So we'll can add and remove easily the packages! Thanx
make rpm support optional? being I'm on a gentoo system atm I do not have rpm installed. Also you might wanna add a check in the configure script for it :) my compile error :( In file included from main.cpp:22: kpackwizardclass.h:41:24: rpm/rpmlib.h: No such file or directory kpackwizardclass.h:42:24: rpm/header.h: No such file or directory
Hey, This is a bug, I wanted to use RPMLIB but due to compatibility with non-rpm systems I am using command-line version but I've forgot to remove those headers. Download KPack 0.1.4-2 or remove #include <rpm/rpmlib.h> #include <rpm/header.h> from src/kpackwizardclass.h and src/SingleRPMInstaller.cpp.
really nice start however I have no idea what commands are being ran, where it's being installed etc. I just tried to install a source code package as a normal user and got no error message of any kind just said it installed, which I know to be not true. when as a normal user it should prompt for root in order to install. Running kpack also generates nothing no dialog, no output on the command line.
There's no error handling in this version. The command being run: - mkdir /tmp/kpack-install - cp [filename] /tmp/kpack-install - tar -xfz OR -xfj [filename.tar.bz2/filename.tar.gz] - cd [source directory] - ./configure - make -n [for progressbar] - make - kdesu --noignorebutton -d --caption Kpack -c "make install" Without error handling, KPack cannot tell you you have no KDESU installed. I can implement my own dialog, but if I use KDESU KPack will look more integrated into KDE. I will fix it in future versions, and implement KDESU dialog AND KPack's own root dialog.
I have kdesu. but it still never prompted me anything?
Try current version.
SlackWare TGZ package support?
Currently no - I need to know how to use it.
any slackware .tgz package contains binaries and libraries (including devel). 1. it is a tar.gz file 2. to install -> tar -zxvf -C / (root) 3. there's a folder "/install" which contains a script file "doinst.sh" which creates symbolic links and removes when uninstalled. if we extract the slackware packages on '/' (root) then it is like installing. and executing the /install/doinst.sh will create symbolic links etc., required. To remove, just delete the files which are present in the tgz files in the filesystem and remove the symbolic links which are present in doinst.sh file. that's it.
A package manager that handles both RPM and DEB packages as well as stuff built from source is a much needed application. However, one of the major things which it needs to do is to track dependencies. For example: I install an RPM and it has unresolved dependencies on some libraries. The package manager needs to check and see if I actually have these libraries installed and if so, go ahead and install the RPM. I have a library that I built from source and I want to know which other stuff depends on it. The package manager should be able to tell me this by building a data base from the ld.so.cache.
cze wlasnie sciagam twoj instalator. mam pytanie. Czy bedzieon mial/ ma mozliwosc instalowania programu z mozliwoscia zmieniania lokacji i dowiazywanie dynamicznych bibliotek( cos jak w pcbsd0 A TAK SWOJA DROGA TO BARDZO DOBRY POMYSL. DZIEKI
Siema Po ang trzeba tu pisać:( Jak na razie kodu jest mało i mogę wstawić wszystko - ale requesty pisz po angielsku:)
However installation without dependencies is not so useful. Also, could the distributor create some more complex install package, e.g. to display some instructional text? It would be a good idea to use Smart Package Manager as backend - it already supports a variety of package formats and is able to handle dependencies.
I can implement everything - graphics, text or sound. Just need an idea.
great job sabby, for the moment i'm just getting a four zero four instead of the tarball, but i've got a question for you? is KPack some kind of KPackage (dist. pm. front end) or is it able to create executable installers (like BitRock ~http://www.bitrock.com~ or like win32 installers) anyway great job and hope the download link will get corrected
Damn, thanks! I didn't know download link was broken... KPack is flexible so I can implement any type of install. In next version automatic compiling (in future QMake projects too) will be supported with progressbar.