This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Hi all,

I am building from the 1.10 branch for the first time and noticed that the included spec file in this release generates two RPMs like Red Hat normally does with their OS' releases for Wireshark.

I'm looking to have a single RPM for ease of installations. The last time I built an RPM was from 1.8.x and it still had a single RPM. I am somewhat spec "literate" and think it wouldn't be too difficult to make the required changes, but then again there is a lot more content in the new spec file compared to this older one and I am a bit unsure of any chronological dependencies that might come into play if I started combining, for example the "%install" and "%install gnome" sections.

Before I get started, wondering if there is a ./configure option or something similar that automatically generates a spec file for a single RPM?

Thanks for reading, J

asked 22 Jan '14, 10:41

jorwex's gravatar image

jorwex
6335
accept rate: 0%

More info. I see this in the changelog for the spec:

  • Mon Feb 6 2013 Jeff Morriss **- Overhaul to make this file more useful/up to date. Many changes are based on Fedora's .spec file. Changes include:
    • Create a separate wireshark-gnome package (like Redhat).**
    • Control some things with variables set at the top of the file.
    • Allow the user to configure how dumpcap is installed.
    • Allow the user to choose some options including GTK2 or GTK3.
    • Greatly expand the BuildRequires entries; get the minimum versions of some things from 'configure'.
    • Install freedesktop files for better (free)desktop integration.
(22 Jan '14, 10:59) jorwex

I removed the comment that Jeff is responding to (I had it earlier here) because I thought it was worthy of a separate post: http://ask.wireshark.org/questions/29106/different-so-dependencies-between-normal-build-and-rpm

(22 Jan '14, 12:10) jorwex

The reason for the package separation is both to support installing tshark on machines without GTK/X and to allow for the eventual migration to a Qt GUI (the development version now has 3 RPMs: wireshark, wireshark-gnome, and wireshark-qt: you can install either, both, or neither of the GUIs).

No, there isn't an option to go back to the one-RPM version. You're right it should be possible to hack it up to work but then you'd have to redo that work again in the next stable version because a lot changed to support the Qt GUI package. There was another user who was having some problems and eventually went back and just used the 1.8 spec file--and reported success in doing so. Not that I'd really encourage you to do that...

Is there a particular reason you really need one RPM file?

As for the libwiretap.so.2 problem: that sounds vaguely familiar but I thought it was fixed. Do you have a Wireshark installed which supplies libwiretap.so.2? If you do, the workaround is probably to remove that installed version before building your RPM. But I really thought we fixed that... Need to do some research (no promises--I'm quite short on time these days). (And actually the machine where I build my 1.10 RPMs has Wireshark 1.8 installed, that package supplies libwiretap.so.2, and my packages build just fine. Hmm...)

permanent link

answered 22 Jan '14, 11:51

JeffMorriss's gravatar image

JeffMorriss ♦
6.2k572
accept rate: 27%

Thanks for the info!

No great reason for the single rpm. I think I can live with it.

Wow I had the Red Hat el6-supplied 1.2.x installed on the build machine. Trying build again now that I have removed it...

(22 Jan '14, 12:14) jorwex

WORKED! You are awesome Jeff! That bug must still remain somehow.

(22 Jan '14, 12:15) jorwex

OK I found the fix I was thinking of (r48582) and it is fixed in the 1.10 series (see bug 6011). So I'm not sure what's going on with your libwiretap problem...

(22 Jan '14, 13:55) JeffMorriss ♦
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×13
×11

question asked: 22 Jan '14, 10:41

question was seen: 2,009 times

last updated: 22 Jan '14, 13:55

p​o​w​e​r​e​d by O​S​Q​A