Well...

fc2 vs fc4 is expected... If there were a reliable way to figure out the
release, but there ain't so don't go there...
  Newer versions of rpmbuild start to support parameters, but you can't yet
depend on finding them out there...

SourceForge .tgz is the .tgz on SourceForge, which should be what is
installed via the .src.rpm package.  So I don't understand why you need to
change that.

Copyright vs License - could be a booboo...

Those files are supposed to be in the .tgz (in the packages/RedHat
directory).

What I have is the usual buildmeister setup:

.rpmmacros
/BUILD
/RPMS/i368
/RPMS/noarch
/SRPMS
/SOURCES
/SPECS

With the various files in SOURCES.  Somebody who actually understands rpms
could probably clue me in as to how to make the rebuild work seamlessly.

-----Burton

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Randy Gordey
Sent: Tuesday, October 04, 2005 11:59 AM
To: [email protected]
Subject: [Ntop-dev] rpmbuild ntop 3.2rc2 under Fedora Core 4

[EMAIL PROTECTED] ~]#rpmbuild -ta ntop-3.2rc2.tgz ...<snip>...
...</snip>...
Checking for unpackaged file(s): /usr/lib/rpm/check-files /var/tmp/ntop-root
Wrote: /usr/src/redhat/SRPMS/ntop-3.2rc2_fc4-1.src.rpm
Wrote: /usr/src/redhat/RPMS/i386/ntop-3.2rc2_fc4-1.i386.rpm
Wrote: /usr/src/redhat/RPMS/i386/ntop-debuginfo-3.2rc2_fc4-1.i386.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.5471
+ umask 022
+ cd /usr/src/redhat/BUILD
+ cd ntop-3.2rc2
+ rm -rf /var/tmp/ntop-root
+ exit 0

I installed the RPM and it is running great!!!!! Thanks for a great product!

Although, I had to have made the following changes and then tar it back up
before the build:

--- OldRedHat/ntop.spec 2005-10-04 07:21:19.000000000 -0400
+++ NewRedHat/ntop.spec 2005-10-04 10:39:14.000000000 -0400
@@ -5,9 +5,9 @@
 ## 1 would be the second, etc.
 #
 %define rpmversion 3.2
-%define rpmsuffix rc1
+%define rpmsuffix rc2
 %define rpmrelease 1
-%define rpmdistro fc2
+%define rpmdistro fc4
 ##
 ## Pick ONE of these sets as appropriate  # @@ -39,7 +39,7 @@
 Source3: ntop.conf.sample
 Patch1: version.patch
 
-Copyright: GPL
+License: GPL
 Group: Applications/System
 BuildPrereq: glibc, glibc-devel, gcc, cpp, gawk, autoconf, automake,
binutils, openssl, openssl-devel, gdbm, gdbm-devel, libpcap, z lib-devel
 Requires: glibc, openssl, gdbm, libpcap, chkconfig
--- OldRedHat/version.patch     2005-10-04 10:29:41.000000000 -0400
+++ NewRedHat/version.patch     2005-10-04 10:31:40.000000000 -0400
@@ -4,7 +4,7 @@
  HAS_ERROR=
  HAS_WARNING=
  
--NTOP_VERSION_EXTRA=""
+-NTOP_VERSION_EXTRA=" SourceForge .tgz"
 +NTOP_VERSION_EXTRA="SourceForge RPM"
  
  echo
@@ -15,7 +15,7 @@
  HAS_ERROR=
  HAS_WARNING=
  
--NTOP_VERSION_EXTRA=""
+-NTOP_VERSION_EXTRA=" SourceForge .tgz"
 +NTOP_VERSION_EXTRA="SourceForge RPM"
  
  echo


I also had to have copied the following file to the current directory (where
I ran rpmbuild) from ./ntop-3.2rc2/packages/RedHat/

ntop.conf.sample
ntop.init
ntop.logrotate


I see where they are defined in the spec file as:
Source: %{name}-%{rpmversion}%{rpmsuffix}.tgz
Source1: ntop.init
Source2: ntop.logrotate
Source3: ntop.conf.sample
Patch1: version.patch

...and installed here:
install -c -m0755 %{SOURCE1} $RPM_BUILD_ROOT/etc/rc.d/init.d/ntop
install -c -m0644 %{SOURCE2} $RPM_BUILD_ROOT/etc/logrotate.d/ntop
install -c -m0700 %{SOURCE3} $RPM_BUILD_ROOT/etc/ntop.conf.sample


However, I am not savvy enough to specify the build environment as the
source location for the install. The 'patch' seemed to work for the correct
location as specified but three 'install' lines choke finding the right
path. 

Question: How can I make my rpm without having those three files handy
outside the .tgz? Is this how it is suppose to work?

Again, thank you!


Kind Regards,
~Randy Gordey


Fedora Core release 4 (Stentz)+
patch-2.5.4-24
rpm-build-4.4.1-22_49.rhfc4.at
rpm-4.4.1-22_49.rhfc4.at
gcc-4.0.1-4.fc4
cpp-4.0.1-4.fc4
glibc-2.3.5-10.3
make-3.80-7
autoconf-2.59-5_11.rhfc4.at
automake-1.9.5-1_24.rhfc4.at
gdbm-1.8.0-25






_______________________________________________
Ntop-dev mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev

_______________________________________________
Ntop-dev mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-dev

Reply via email to