Bug 131266 - update spec to include subpackages
update spec to include subpackages
Product: Fedora
Classification: Fedora
Component: lam (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jason Vas Dias
Brian Brock
: FutureFeature
Depends On:
  Show dependency treegraph
Reported: 2004-08-30 12:57 EDT by Greg Kurtzer
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-03 10:43:54 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Greg Kurtzer 2004-08-30 12:57:20 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030422

Description of problem:
<lon> wow, that's a pretty spec file
<gmkurtzer> hehe... your too kind. ;)
<gmkurtzer> actually, that is jeff's stuff.
<lon> still, you should pull down the lam source rpm from red hat and
look at the spec file ;)
<gmkurtzer> I did it at one point, but not recently. I will do so.
<gmkurtzer> FC2, or RHEL SRPM?
<lon> i'd look @ fc2
<lon> probably more recent
<lon> it's ugly.
<lon> but works.
<gmkurtzer> hehe...
<gmkurtzer> ahh, the reason that we didn't use that rpm is because it
doesnt create any subpackges
<gmkurtzer> and our node file system is about 30MB
<gmkurtzer> that would bump it to 35
<lon> ah
<lon> nod
<lon> You can file a bugzilla against it - toss in that spec link you
sent me.  :)  I can look @ it for FC4

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Uhmm... build the RPM
2. These fields are rather not needed for an RFE!

Additional info:
Comment 1 Lon Hohberger 2004-08-30 12:59:02 EDT
Thanks for the post.
Comment 2 Jason Vas Dias 2005-06-03 10:43:54 EDT
Presumably whatever changes were required to the spec file have been
made - link above is no longer there. If there's any issues with the
current  2.0.2-3 release, please open another bug.

Note You need to log in before you can comment on or make changes to this bug.