December 2006 - openSUSE Packaging - openSUSE Mailing Lists

[opensuse-packaging] Packaging php-pear modules
by Marcus Hüwe 15 Dec '06

15 Dec '06

Hi, i've a general question about packaging php-pear modules. If you install pear-module via the commandline tool, pear manages each module in its "own" packagemanagement (it takes care that all dependencies etc. are installed...). Now if you install a (suse) php-pear-* rpm package the pear packagemanager doesn't know that this certain packages is installed. What about registering this package by the pear packagemanager too? For example the following could be added to the spec files: %post # make the package known to the pear-packagemanager pear install --nodeps --register-only PACKAGE.xml %postun # remove the package from the pear-packagemanager pear uninstall --nodeps --register-only PACKAGE (maybe some arguments should be added to the pear call..). But this maybe leads to some problems too. One possible problem could be that the user removes the pear-package via the pear commandline tool but the package still exists in the rpm database..?! What do you think about this? Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 4

[opensuse-packaging] suse-kernel-module-package
by Andreas 12 Dec '06

12 Dec '06

I am trying to build an rpm for the fuse package that includes the optionally built kernel module. (It is necessary to use the ntfs-3g program to achive write access on ntfs partitions). So far I simply put the line %suse_kernel_module_package in my specfile, hoping that magically a kmp-rpm will show up . That doesn't happen though :( Does anyone have a hint as to what I have to add to the specfile to make it work? -- Gruß & Happy Holidays! Andreas --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 5

[opensuse-packaging] Google SoC project: A Package Build System - APBuDdy
by Rajagopal Natarajan 05 Dec '06

05 Dec '06

The main purpose of APBS is providing a semi-automatic tool for creating of high quality packages for more distributions. APBS consists from two parts: Abstract Package Build Description: This is an extensible XML based description, which can be used to specify build description for more distributions and version in a single file. Currently supported are RPM and Deb files. Abstract Package Build Tool: This is a tool, which helps users to create packages. The tool uses Abstract Package Build Description as an intermediate format. APBT acts as a container engine for miscellaneous actions (packaging steps or guesses - its "artificial intelligence") needed for creating the package. APBT selects proper actions and calls them in the proper order. Depending on a source contents, these actions perform needed packaging steps with optional user input. It tries to guess best solution for particular package. For user it acts like a wizard-style application, for the packaging it acts like a engine with sequential execution of required steps. User can modify any packaging step by hand. APBT is easily extensible. It allow you to add new rules for package description and create new types of packages. It is written in Ruby and in future the user interaction frontend can be integrated with the OpenSuSE Build System. Current implementation supports autoconf based packages and perl packages. The tree is now open for the future development. Feel free to join. The tool is available at http://en.opensuse.org/Abstract_Package_Build_Description TODOs: - Currently it has only basic support for scriptlets. It should be improved in future. (This part of packaging is strictly distribution dependent.) - Support guesses for BuildRequires. Some simple ideas exists (e. g. analyze configure.in to check for some dependencies), but complex solution is far above the Google SoC project. - Support more types of packages and more rules. - Automatic error handling ability - Features to help ISVs who want to ship their windows package with wine(may be a plugin, making use of the extensibility that is available) - Checkpoints - Support tools for file list modification (e. g. %find_lang). Thanks to my GSOC mentor Stanislav Brabec for guiding me at each step. -- N. Rajagopal, Visit me at http://www.rajagopal.tk

1 0

[opensuse-packaging] looking for SuSE rpmlint packager
by Nadia Derbey 05 Dec '06

05 Dec '06

Hi, Can somebody redirect me to the rpmlint packager for SuSE Linux (I'm using rpmlint-0.78-0.pm.1 on a SL 10.1) -or give me a way on how to find him/her: when running rpmlint on a package for SuSE Linux, I've got 2 "false" warnings and I've been told on the rpmlint-discuss mailing list that this should be fixed at the rpmlint pacakger level. see the thread "strange rpmlint behavior" at https://www.zarb.org/pipermail/rpmlint-discuss/2006-November/thread.html and ticket #54 at rpmlint bug tracker (http://rpmlint.zarb.org/cgi-bin/trac.cgi/ticket/54) Regards, Nadia --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

3 5

Re: [opensuse-packaging] looking for SuSE rpmlint packager
by Dominique Leuenberger 05 Dec '06

05 Dec '06

>>> Reply on 05-12-2006 13:01:48 <<< > > Hi, > > Can somebody redirect me to the rpmlint packager for SuSE Linux (I'm > using rpmlint-0.78-0.pm.1 on a SL 10.1) -or give me a way on how to find > > him/her: when running rpmlint on a package for SuSE Linux, I've got 2 > "false" warnings and I've been told on the rpmlint-discuss mailing list > > that this should be fixed at the rpmlint pacakger level. > > see the thread "strange rpmlint behavior" at > https://www.zarb.org/pipermail/rpmlint-discuss/2006-November/thread.html > > and ticket #54 at rpmlint bug tracker > (http://rpmlint.zarb.org/cgi-bin/trac.cgi/ticket/54) Nadia, the .pm. in the package name shows that it's a package coming from PackMan. So all the information about the packager can be found at http://packman.links2linux.com/package/rpmlint I hope this helps you a bit, Dominique --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-packaging+help(a)opensuse.org

1 0

[opensuse-packaging] Feature request for the build script..
by Anders Norrbring 02 Dec '06

02 Dec '06

I guess this is for Ludwig.. Are there any chances that you can enable installation sources from iso images? Like in YaST/Zen.. It would be really nice to be able to pull the repos directly from the DVD images, instead of mounting them at each build. -- Anders Norrbring Norrbring Consulting

2 3