On Mon, Jan 8, 2018 at 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
>
> Then I would, by hand, untar
Thanks for all the input... very interesting.
But I decide to go a head can create a new package
which eliminates all the questions about lifecycles
dependencies, licenses, etc
Again, thanks for all the input!
steved.
On 01/08/2018 12:21 PM, Steve Dickson wrote:
> Hello,
>
> Is it a probl
On Mon, 2018-01-08 at 12:21 -0500, 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
>
> Then I would, by hand,
Dne 8.1.2018 v 18:21 Steve Dickson napsal(a):
> 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
>
> Then I would, by hand, untar Sour
On 2018-01-08 17:21, 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
Then I would, by hand, untar Source1 into Source0 direc
On Mon, Jan 8, 2018 at 3:38 PM, Fernando Nasser wrote:
> On 2018-01-08 3:07 PM, Nico Kadel-Garcia wrote:
>>
>> On Mon, Jan 8, 2018 at 2:32 PM, Fernando Nasser
>> wrote:
>>>
>>> On 2018-01-08 12:21 PM, Steve Dickson wrote:
Hello,
Is it a problem for a package to pull from two d
On 2018-01-08 3:07 PM, Nico Kadel-Garcia wrote:
On Mon, Jan 8, 2018 at 2:32 PM, Fernando Nasser 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.
On Mon, Jan 8, 2018 at 2:32 PM, Fernando Nasser 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.c
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
Important questions:
1) Are the lifecycles the sam
Hi,
It can be done but it's a PITA to maintain and it's a very bad idea to do if
the two packages are actually two different projects with different lifecycle
expectations, legalities, etc
See the convolutions of the %setup macro
Regards,
--
Nicolas Mailhot
__
Ben Rosser wrote:
> On Mon, Jan 8, 2018 at 12:58 PM, Rob Crittenden wrote:
>> Florian Weimer wrote:
>>> On 01/08/2018 06:21 PM, Steve Dickson wrote:
Is it a problem for a package to pull from two different
upstream tar balls? Basically have
Source0:http://server.com/package1/pa
On Mon, Jan 8, 2018 at 12:58 PM, Rob Crittenden wrote:
> Florian Weimer wrote:
>> On 01/08/2018 06:21 PM, Steve Dickson wrote:
>>> 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:htt
Florian Weimer wrote:
> On 01/08/2018 06:21 PM, Steve Dickson wrote:
>> 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
>>
>> Then I would, by hand
On 01/08/2018 06:21 PM, Steve Dickson wrote:
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
Then I would, by hand, untar Source1 into Source0 directory.
2018-01-08 11:21 GMT-06:00 Steve Dickson :
> 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
>
> Then I would, by hand, untar Source1 int
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
Then I would, by hand, untar Source1 into Source0 directory.
Before do the work I want to make s
On 18/01/17 08:29, Ding Yi Chen wrote:
On version 4.0.0, we merge all the sub projects like parent, api, common,
client and server
into zanata-platform.
At this point, we have no plan to pack server as RPM yet, because there too
many dependencies to solve
(Maven and Java-scripts)
Should I c
On version 4.0.0, we merge all the sub projects like parent, api, common,
client and server
into zanata-platform.
At this point, we have no plan to pack server as RPM yet, because there too
many dependencies to solve
(Maven and Java-scripts)
Should I continue to call it zanata-client, or rename
18 matches
Mail list logo