kadu and rpmbuildupdate - 8.09.2012

[tele]

1.
From synaptic:  rpmbuildupdate:
depending: perl(RPM4)

2.
Kadu from testing repository not have plug and not have network ( Sieć )
I compile from source (only for 32 bit)  , and working .

Source
download.kadu.im/stable/kadu-0.12.2.tar.bz2

 mkdir build
  cd build/
  cmake ..    
  make -j2  
( make -j2 is for 32bit , make -j3 is for 64bit , make -j4 is for 3 processor core )

Example depencies for compile : libxscrnsaver-devel (screen saver) , libaspell-devel, libidn-devel.

Edit : 19.11.2012
Now I know , make -j2 it does not matter
Protocol gadu and jabber are in 0.12.0 in plugins, but in .spec file is:

Code: [Select]

%build
%cmake_qt4 -DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_BUILD_TYPE=Release \
-DBUILD_PLUGINS=OFF
I compiled and I used

%files -n %{name}-plugins

and

%files -n %{name}-plugins_protocols

but this not working, how I want.
I wanted plugins separately and kadu must work , but if if I will  install without plugins ( it means that it will not )
Icon tray not working, application closes.
I wrote to the forum question, which files are responsible for this exactly.

Neal, ghostbunny , something you can advise and help and see?
In a moment I upload my kadu, spec file etc. and I will give link.

1. Spec file:
http://wklejto.pl/138931

2. Read below.

[ghostbunny]

Hi,

i think you can't move all plugins into the plugin/_protocol packages.

What shows the terminal if you have installed your binary and launched it from there?

[tele]

I don't want " all in one "
so

I  create from plugins  : -plugins and -plugins_protocol  (plugin protocol this is jabber and gadu protocol )
( from ~/src/rpm/BUILDROOT/kadu-0.12.2-1pclos2012.i386/... )
example:
- kadu
- emots
- icons
- sounds
- l10n
- devel
- plugins
- plugins_protocols


I split the files into 2 sections.
Maybe someone does not want all plugins, so I split,
but I did it wrong, plugins protocol is not everything what I want,
missing plugin  " docking " --> service icon in the System Tray.
I do not know which files to transfer from -plugins to -plugins_protocol

You can also add files from - plugins_protocols and docking files to -kadu,
but I'm not sure  which they are. I asked on another forum and wait for a response.
because in plugins we have similar plugins:
desktop_docking
docking --> probably that I'm looking for
qt4_docking
qt4_docking_notify

[Links deleted]

Kadu without " - plugins " working, but it is not convenient without " service icon in the System Tray ",
which are in " - plugins " .

I don't checked
BuildRequires:
Requires:
Obsoletes:
Because I don't know how, any advice it's nice welcome. :-)

This is plugin,  I don't have only " -plugins  " package installed and I don't have any errors.

Code: [Select]

$ /usr/bin/kadu
[gg3@localhost Documents]$
Plugins you can add remove from package, but some are needed, example protocols plugins.


Edit:

I doubt a quick answer on the forum there.

http://translate.google.pl/translate?sl=pl&tl=en&js=n&prev=_t&hl=pl&ie=UTF-8&layout=2&eotf=1&u=http%3A%2F%2Fwww.kadu.im%2Fw%2FDocking

his module is not enough to dock Kadu - still need a family unit * _docking to handle different window managers

So It can't be  on separate

I seperate dock files from plugins, docking_notify can be too added.

Code: [Select]

%{_libdir}/%{appname}/plugins/libdesktop_docking.so
%{_libdir}/%{appname}/plugins/libdocking.so
%{_libdir}/%{appname}/plugins/libqt4_docking.so
%{_libdir}/%{appname}/plugins/libqt4_docking_notify.so
%{_datadir}/%{appname}/plugins/configuration/desktop_docking.ui
%{_datadir}/%{appname}/plugins/configuration/qt4-docking-notify.ui
%{_datadir}/%{appname}/plugins/configuration/docking.ui
%{_datadir}/%{appname}/plugins/desktop_docking.desc
%{_datadir}/%{appname}/plugins/docking.desc
%{_datadir}/%{appname}/plugins/qt4_docking.desc
%{_datadir}/%{appname}/plugins/qt4_docking_notify.desc
%{_datadir}/%{appname}/plugins/translations/desktop_docking_cs.qm
%{_datadir}/%{appname}/plugins/translations/desktop_docking_de.qm
%{_datadir}/%{appname}/plugins/translations/desktop_docking_en.qm
%{_datadir}/%{appname}/plugins/translations/desktop_docking_es_ES.qm
%{_datadir}/%{appname}/plugins/translations/desktop_docking_fr.qm
%{_datadir}/%{appname}/plugins/translations/desktop_docking_it.qm
%{_datadir}/%{appname}/plugins/translations/desktop_docking_pl.qm
%{_datadir}/%{appname}/plugins/translations/docking_cs.qm
%{_datadir}/%{appname}/plugins/translations/docking_de.qm
%{_datadir}/%{appname}/plugins/translations/docking_en.qm
%{_datadir}/%{appname}/plugins/translations/docking_fr.qm
%{_datadir}/%{appname}/plugins/translations/docking_it.qm
%{_datadir}/%{appname}/plugins/translations/docking_pl.qm
%{_datadir}/%{appname}/plugins/translations/qt4_docking_notify_cs.qm
%{_datadir}/%{appname}/plugins/translations/qt4_docking_notify_de.qm
%{_datadir}/%{appname}/plugins/translations/qt4_docking_notify_en.qm
%{_datadir}/%{appname}/plugins/translations/qt4_docking_notify_fr.qm
%{_datadir}/%{appname}/plugins/translations/qt4_docking_notify_pl.qm

ghostbunny what you think?
may stay?
Do you you make a new package?



 

[ghostbunny]

mh i probably would place the *docking* libs/files in the main package if the docking is necessary for correct running.

desktop_docking
docking --> probably that I'm looking for
qt4_docking
qt4_docking_notify

Code: [Select]

%{_datadir}/%{appname}/plugins/desktop_docking.desc
%{_datadir}/%{appname}/plugins/docking.desc
%{_datadir}/%{appname}/plugins/configuration/desktop_docking.ui
%{_libdir}/%{appname}/plugins/libqt4_docking.so
%{_libdir}/%{appname}/plugins/libqt4_docking_notify.so
%{_libdir}/%{appname}/plugins/libdesktop_docking.so
%{_libdir}/%{appname}/plugins/libdocking.so


[tele]

Can you do?

Edit:
just read the two posts above, which files add  

or help me how edit spec file, I compile  

[ghostbunny]

i extend the list to

Code: [Select]

%{_datadir}/%{appname}/plugins/desktop_docking.desc
%{_datadir}/%{appname}/plugins/docking.desc
%{_datadir}/%{appname}/plugins/configuration/desktop_docking.ui
%{_libdir}/%{appname}/plugins/libqt4_docking.so
%{_libdir}/%{appname}/plugins/libqt4_docking_notify.so
%{_libdir}/%{appname}/plugins/libdesktop_docking.so
%{_libdir}/%{appname}/plugins/libdocking.so
%{_datadir}/%{appname}/plugins/translations/desktop_docking_en.qm
%{_datadir}/%{appname}/plugins/translations/docking_en.qm
%{_datadir}/%{appname}/plugins/translations/qt4_docking_notify_en.qm

sorry but i'm currently not able to do but what is the problem to search the lines above and move them in the main package?

or just use your list it's also good covers more than mine but i would move the translations (except english) into the i18n package just my opinion

[tele]

I can move above lines.
Problem is , I am a beginner
I'm looking for , how I can I find it:
 - BuildRequires:
   Requires:
   Obsoletes:
 - I write -j2 option like this:  %{make -j2}%{?_smp_mflags} , working but this is correct?
 - For compile with plugins we need amarok or amarok-devel installed , I don't know how to check.
I wan't know for what someone did "kadu_config_pclos"  file, how this work.
Only this.

good covers more than mine but i would move the translations (except english) into the i18n package just my opinion

This is good idea.  

 - I'm going to do.

[ghostbunny]

I'm looking for , how I can I find it:
 - BuildRequires:
   Requires:

This is difficult always check readme and install files in the tarballs or installation help on the apps website. That's the only thing to get them. if the authors doesn't offer this information all you can do is trail and error

start the build and if it aborts because of e.g. glib.h is missing than you will have to install glib-devel and add this to BuildRequires. The same is it with Requires. Start your compiled program from the terminal and look for things like "missing xyz", "failed to load library xyz".

that's a i can say about this.

I don't know the correct use of Obsoletes but mostly it is recommended to add the program it self in any lower  version e.g. you are packaging kadu in version 0.12.2
so you could add

Obsoletes: kadu < 0.12.2
but do this always by using the macros %name and %version this saves time on an next update.
Obsoletes is also used when an newer version does not provide the files like in the pre version. Hope some other packagers jump in to explain this better also if i have said something wrong.

%{make -j2}

this isn't necessary TerryN explained this somewhere in the packagers section or so. The %make marco extends always to make -jx x depends on your processor

- For compile with plugins we need amarok or amarok-devel installed , I don't know how to check.

just check synaptic for "amarok-devel" or "amarok -devel" or "libamarok-devel" or "libamarok -devel" i do not know how the devel package is named. Than install it and add it to BuildRequires if it is necessary for compiling.

[TerryN]

I don't know the correct use of Obsoletes but mostly it is recommended to add the program it self in any lower  version e.g. you are packaging kadu in version 0.12.2
so you could add
Obsoletes: kadu < 0.12.2

Obsoletes is used when a package is renamed or completely replaced by another package.  For example in Samba 3.6 the tools provided by the mount-cifs package have been moved to a new package called cifs-utils.  Therefore this new package has to Obsolete mount-cifs so that it gets removed when cifs-utils is installed.
Package updates automatically Obsolete their previous versions so there is no need to add them in that case (but it does no harm).

Obsoletes and Conflicts mean the same thing to apt/synaptic (i.e. remove the obsoleted/conflicted package when installing this package).
The difference between the two appears with the rpm command:
Obsoletes -> rpm -U will automatically remove the obsoleted package (if installed) and install this package.
Conflicts -> rpm -U will throw an error message if the conflicting package is installed and will not install this package.

Terry.

[tele]

 Ready spec file,
 You can add  or edit %description for your language on-line.
Change  will saved, when you write.
You don't must use login, for edit, it works at once/now .

[Links deleted]

[ghostbunny]

means this that it is working after compiling?

[tele]

I will know after compiling, above files are too edited, and works,  I can now compiling and check, If you like.

[ghostbunny]

yes try, please,translations are always optional you just need to have an English summary and description

[tele]

Edited:

Sorry!
rpm -ivh kadu-0.12.2-1pclos2012.i586.rpm
błąd: Failed dependencies:
        liblibqtsql4 >= 4.8.0 required by kadu-0.12.2-1pclos2012.i586
I added this last time, I will fix this.
 
[Link deleted]

I tested 0.9 kadu in old system , kde (not kde4) and this have plugin,
so maybe in 0.12 kadu , file "kadu config pclos" is not necessary.

This spec file is not perfect, before compilation I was:

Code: [Select]

CMake Warning:
  Manually-specified variables were not used by the project:

    CMAKE_MODULE_LINKER_FLAGS
    DBUS_INTERFACES_DIR
    DBUS_SERVICES_DIR
Need test without  Requires:
# Requires:   %{_lib}xfixes3
# Requires:   %{_lib}x11-common
# Requires:   %{_lib}xext6
# Recommended:   Ntrack-Qt >=010 ; possible not exist for pc-linux package
# Requires:   qca2   >= 2.0.3
# Requires:   %{_lib}indicate-qt
# Requires:   zlib1
# Requires:   %{_lib}idn11
# Requires:   %{_lib}mpdclient2

I wish pclinux in future tools like portage in gentoo, rpmdevtools in fedora  .

[ghostbunny]

This spec file is not perfect, before compilation I was:

Code: [Select]

CMake Warning:
  Manually-specified variables were not used by the project:

    CMAKE_MODULE_LINKER_FLAGS
    DBUS_INTERFACES_DIR
    DBUS_SERVICES_DIR
Need test without  Requires:
# Requires:   %{_lib}xfixes3
# Requires:   %{_lib}x11-common
# Requires:   %{_lib}xext6
# Recommended:   Ntrack-Qt >=010 ; possible not exist for pc-linux package
# Requires:   qca2   >= 2.0.3
# Requires:   %{_lib}indicate-qt
# Requires:   zlib1
# Requires:   %{_lib}idn11
# Requires:   %{_lib}mpdclient2

I wish pclinux in future tools like portage in gentoo, rpmdevtools in fedora  .

the cmake warning isn't a problem that's caused by the cmake macro which defines more than needed and it does not affect the build.

don't know about the requires but could be possible that some plugins wont work without them.