Menu
▾
▴
#8 [RPM building] Rodent >5.2.3 splitting
open
5
2014-02-21
2014-02-02
No
Hi.
In the latest Rodent version (5.2.3) I see a splitting process. The sources are divided and each application (fgr, rodent-diff, rodent-fgr, rodent-fm, rodent-iconmgr) has own directory in /app.
In future, are you going to keep all applications in a single source archive ? Or will Rodent applications be maintained separately ?
I must decide if build a single Rodent package or split it in different RPMs.
With the current version of librfm, each of the programs in the apps directory can be compiled and installed separately. But if all programs are to be compiled and installed, the easiest way is to configure and compile from the top source directory. This will take care of all packages in apps.
This makes it easier to work on different programs and add new ones, which I plan to do.
Whenever I release any program in the apps directory as a separate package, I will have previously have released the "big" meta single source archive which contains it.
If you wish to split the Rodent package or keep it as a meta package (or even do both) the decision is entirely up to you.
Currently each app will build it's own rpm spec file which I've tested so far on OpenSUSE. To build a CentOS spec file, "./configure --with-centos". The top level meta package "make rpm" is still not working. That is why there is no rpms nor debs in this release. But I hope to get that fixed soon.
HTH
Okay.
configure files in /apps/rodent-? have different options compared with configure in top source directory.
Is there any problems about that?
Last edit: Antonio Trande 2014-02-07
There should be no problem with different configure options in rodent/apps. All options specified at top level are passed down to rodent/apps subdirs. Options which do not apply are just ignored.