On 2018-01-08 3:07 PM, Nico Kadel-Garcia wrote:
On Mon, Jan 8, 2018 at 2:32 PM, Fernando Nasser <fnasser@xxxxxxxxxx> wrote:
On 2018-01-08 12:21 PM, Steve Dickson wrote:
Hello,
Is it a problem for a package to pull from two different
upstream tar balls? Basically have
Source0: http://server.com/package1/package1.tar
Source1: http://server.com/package2/package2.tar
It happens all the time. Subversion used to do this a lot, when the
requirement for the "swig" library was more recent than what was in
Fedora. It also happens quite a lot for RHEL and EPEL packages, where
the necessary versions of various libraries may conflict with the
stable, standard library used by other tools.
Hum... not sure if this was good form. An important security fix may
fail to be applied to this "hidden" library for one thing.
This is supposed to be handled by having a versioned package for the
alternative library version that could then be used by this package (as
opposed as the default Fedora version of it).
This has similar problems as using the Maven shadow plugin in Fedora
Java builds (which is AFAIK also discouraged).
--Fernando
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
