On 10/19/2016 11:38 AM, Jason L Tibbitts III wrote:
"MM" == Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> writes:
MM> Ha. I've looked at the regular redhat-rpm-config macros so I'm
MM> partially-innoculated. But generally, doing... creative... things
MM> there is better than putting more complication in each spec file.
I've been spending a lot of time in there and in RPM macro stuff in
general, doing things far worse than this. So if there are specific
needs, we can try to come up with something. I note with trepidation
that Red Hat already did something a bit like this with SCLs, but I
wouldn't recommend using those macros as any kind of an example.
And, you know, maybe someone (who knows or cares a lot more than I do)
could look back at relocatable RPMs and what the issues were there.
That was all a big "do not use" by the time I got involved so I can't
really say anything about them.
This isn't really directly applicable, but I've been playing around with
building RPMs into /opt and creating a system of stackable dependencies
among them. Some more info is here:
https://github.com/altccrpms/info/wiki
https://github.com/altccrpms/altcc-rpm-macros
One challenge is that once you move out of /usr, you can no longer rely
on the filesystem package to own the top level directories so I've had
to add things like:
%files
%{?altcc:%altcc_files %{_bindir} %{_libdir} %{_mandir}/man1}
to own the appropriate directories.
But I have been pretty happy with being able to build parallel
installable rpms of different versions of packages while maintaining
some automatic dependencies as well. Packages provide/require are
prefixed with their install location so they have a separate namespace.
It also has been fairly straightforward to redefine _prefix and
_sysconfdir and that works for most packages.
- Orion
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA/CoRA Division FAX: 303-415-9702
3380 Mitchell Lane orion@xxxxxxxxxxxxx
Boulder, CO 80301 http://www.cora.nwra.com
_______________________________________________
packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx