> > Even if the .spec files _were_ installed with every package, the > 1 in 100000 users that look at 1-5 out of the 2000 .spec files > that would be installed, would then have to get some src.rpm code > likely to get going anyway. After they've learned what they > could from the spec file (about 15 seconds worth) they would have > little use for them anymore. .spec files are not documentation > on how to build packages. The HOWTO is a start, and the book > Maximum RPM is a finish. The book is free download from rpm.org. When last I looked, Maximum RPM was seriously out of date; it applies to rpm 2.x and 3 is very different, and presumably 4.0 will make obsolete anything anyone's writing/written for 3. Mike Just what's in a src.rpm that's so useful that is NOT in the spec file? _______________________________________________ Redhat-devel-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-devel-list
- Re: binary packages to include specs Mike A. Harris
- Re: binary packages to include specs Levente Farkas
- Re: binary packages to include specs Mike A. Harris
- Re: binary packages to include specs Levente Farkas
- Re: binary packages to include specs Frank Hale
- Re: binary packages to include specs Alan Shutko
- Re: binary packages to include specs John Summerfield
- Re: binary packages to include specs Mike A. Harris
- Re: binary packages to include specs Levente Farkas
- Re: binary packages to include specs Mike A. Harris
- Re: binary packages to include specs John Summerfield
- Re: binary packages to include specs Alan Shutko
- Re: binary packages to include specs Mike A. Harris
- Re: binary packages to include specs John Summerfield
- Re: binary packages to include specs Thomas Dodd
- Re: binary packages to include specs John Summerfield
- Re: binary packages to include specs Mike A. Harris
- Re: binary packages to include specs John Summerfield
- binary packages to include specs Viorel Anghel