Quote:
Originally Posted by unSpawn
Two ways, IMHO:
I. 'install /some/file /home/one' and hardcode the location (%files) of the file. This RPM should then *never* be distributed because it isn't compliant.
II. Or you could make it a post-install section shellscript in which you figure out if there is a /home and if there is a user one, and then install the files. You see, installs do not install files in ~/ (OK, with RPM you can --relocate). The general idea is the installation provides central resource or configuration files in /etc or /usr/local/etc (or whatever else location the FSSTND, LSB or FHS mandates) and a user can copy those files to ~/ for customisation. It is then the application's choice to source files or read configuration files in a certain order and in certain locations.
|
i tried this but it fails
Code:
Summary: GNU munna
Name: munna
Version: Beta
Release: FC7
Source0: %{name}-%{version}.tar.gz
License: GPL
Group : Utilities/System
URL : http://munna.com/
Packager: {%Packager}
%description
The GNU indent program reformats C code to any of a variety of
formatting standards, or you can define your own.
%prep
%setup -q
%build
make
%install
%clean
rm -rf %{buildroot}
%files
$HOME/one/munna
rpmbuild -ba munna-Beta.spec
can you please rewrite this code
please help me
thank you in advance
