On Monday, November 14, 2016 4:37:57 PM CET Peter Robinson wrote:
> On Mon, Nov 14, 2016 at 3:37 PM, Pavel Raiskup wrote:
> > On Wednesday, September 21, 2016 12:55:48 PM CET Jason L Tibbitts III wrote:
> >> First off, the guidelines have:
> >> https://fedoraproject.org/wiki/Packaging:Guidelines#N
On Mon, Nov 14, 2016 at 3:37 PM, Pavel Raiskup wrote:
> On Wednesday, September 21, 2016 12:55:48 PM CET Jason L Tibbitts III wrote:
>> First off, the guidelines have:
>> https://fedoraproject.org/wiki/Packaging:Guidelines#Noarch_with_unported_dependencies
>>
>> I've been assuming that you're talk
On Wednesday, September 21, 2016 12:55:48 PM CET Jason L Tibbitts III wrote:
> First off, the guidelines have:
> https://fedoraproject.org/wiki/Packaging:Guidelines#Noarch_with_unported_dependencies
>
> I've been assuming that you're talking about the BuildRequires: case.
> If you're just talking
On 10/03/2016 08:53 AM, Pavel Raiskup wrote:
> Even more interesting, %arm is not on ExclusiveArch list for
> 'vim-syntastic-d' package, while the build on arm machine succeeded:
> http://koji.fedoraproject.org/koji/taskinfo?taskID=15919447
I drive-by fixed the ldc package on arm last night (I don
On Monday, October 3, 2016 8:53:41 AM CEST Pavel Raiskup wrote:
> On Monday, October 3, 2016 8:12:50 AM CEST Pavel Raiskup wrote:
> > On Thursday, September 22, 2016 12:45:32 PM CEST Pavel Raiskup wrote:
> > > Thanks a lot for this discussion. I'll go (probably) the hacky
> > > ExclusiveArch way,
On Monday, October 3, 2016 8:12:50 AM CEST Pavel Raiskup wrote:
> On Thursday, September 22, 2016 12:45:32 PM CEST Pavel Raiskup wrote:
> > Thanks a lot for this discussion. I'll go (probably) the hacky
> > ExclusiveArch way, just because I want to give it a try. Once this
> > becomes too tiring
On Thursday, September 22, 2016 12:45:32 PM CEST Pavel Raiskup wrote:
> Thanks a lot for this discussion. I'll go (probably) the hacky
> ExclusiveArch way, just because I want to give it a try. Once this
> becomes too tiring (because the package has non-trivial amount of
> run-time-only dependenc
> "PR" == Pavel Raiskup writes:
PR> The design issue (probably hard to solve) is that there is no
PR> automatic way to _not_ include such package into particular ARCH yum
PR> repo; and we rather bother packagers.
I'm not entirely sure how the compose tools would that a particular
dependency
On Wednesday, September 21, 2016 12:55:48 PM CEST Jason L Tibbitts III wrote:
> First off, the guidelines have:
> https://fedoraproject.org/wiki/Packaging:Guidelines#Noarch_with_unported_dependencies
>
> I've been assuming that you're talking about the BuildRequires: case.
> If you're just talking
First off, the guidelines have:
https://fedoraproject.org/wiki/Packaging:Guidelines#Noarch_with_unported_dependencies
I've been assuming that you're talking about the BuildRequires: case.
If you're just talking about the case where you can build it anywhere
because you're just copying files around
On Wednesday, September 21, 2016 11:57:06 AM CEST Jason L Tibbitts III wrote:
> > "PR" == Pavel Raiskup writes:
>
> PR> Here comes the same argument as with ExclusiveArch .. I don't want
> PR> to, because this _is_ noarch package and _is_ expected to work on
> PR> all arches, at some point.
>
> "PR" == Pavel Raiskup writes:
PR> Here comes the same argument as with ExclusiveArch .. I don't want
PR> to, because this _is_ noarch package and _is_ expected to work on
PR> all arches, at some point.
It's not noarch, sorry. It doesn't work on all architectures,
regardless of whether it
On Wednesday, September 21, 2016 11:37:09 AM CEST Jason L Tibbitts III wrote:
> > "PR" == Pavel Raiskup writes:
>
> PR> What's should packager do in such case? Recap: noarch package
> PR> depends on arch-dependant package, which is not available
> PR> everywhere.
>
> Then the package is not
> "PR" == Pavel Raiskup writes:
PR> What's should packager do in such case? Recap: noarch package
PR> depends on arch-dependant package, which is not available
PR> everywhere.
Then the package is not noarch. Make it archful, add ExcludeArch:
appropriately.
- J<
__
14 matches
Mail list logo