-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jesse Keating wrote:
> On Wednesday 16 August 2006 13:50, Clark Williams wrote:
>> Gladly, but I have no idea where that repo is :). Should I just pull
>> the SRPM from an extras repo?
>
> Sure you can do that... I've attached it here too.
>
Thanks, comments below
>
> %install
> rm -rf $RPM_BUILD_ROOT
> make DESTDIR=$RPM_BUILD_ROOT install
> # make the default.cfg link
> cd $RPM_BUILD_ROOT/%{_sysconfdir}/%{name}
>
> %if 0%{?fedora:1}
> if [ -f fedora-%{fedora}-%{_target_cpu}-core.cfg ]; then
> ln -s fedora-%{fedora}-%{_target_cpu}-core.cfg default.cfg
> fi
> %endif
>
> # if we haven't created a default link yet, try to do so as devel
> if [ ! -f default.cfg ]; then
> if [ -f fedora-development-%{_target_cpu}-core.cfg ]; then
> ln -s fedora-development-%{_target_cpu}-core.cfg default.cfg
> else
> ln -s fedora-development-i386-core.cfg default.cfg
> fi
> fi
>
Here's the only real difference between your spec file and mine. Mine
just has an unconditional symlink from development-i386 to default. As
I read your logic, if the fedora tag is set, use that for setting the
default symlink. Then if we haven't set default.cfg, if the target_cpu
is set, use it to link to development, else default to development-i386.
I think that will work for me. Michael/Seth, what do you guys think?
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFE42EuHyuj/+TTEp0RAqvuAKCKBC3UlzvzFrvGM7YQkm9PyOeyFQCgjJK+
3T9rM/JucfBjODWTEOnnDvA=
=6J4p
-----END PGP SIGNATURE-----
--
Fedora-buildsys-list mailing list
Fedora-buildsys-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
