Rex Dieter wrote:
> I'd like to be able to conditionalize some package features depending on
> if
> epel repo is enabled or not. One way to accomplish that goal is if epel-
> release defined some macro, say, something like %{epel}, similar to
> %{feodra} or %{rhel}
Followup, after poking nirik
Jeff Sheltren wrote:
> On Sat, Nov 15, 2014 at 10:55 AM, Kevin Fenzi
> wrote:
>
>>
>> The macros.epel file is missing?
>>
>> kevin
>>
>>
> Looks like it didn't make it in the latest patch, but here it is from the
> first patch:
>
> --
> diff --git a/macros.epel b/macros.epel
> new file
On Sat, Nov 15, 2014 at 10:55 AM, Kevin Fenzi wrote:
>
> The macros.epel file is missing?
>
> kevin
>
>
Looks like it didn't make it in the latest patch, but here it is from the
first patch:
--
diff --git a/macros.epel b/macros.epel
new file mode 100644
index 000..fb4413f
--- /dev/nu
On Tue, 11 Nov 2014 14:00:18 -0600
Rex Dieter wrote:
> OK (attached).
The macros.epel file is missing?
kevin
pgpwyHWUBWXXS.pgp
Description: OpenPGP digital signature
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
https://admin.fedora
On Tue, Nov 11, 2014 at 2:00 PM, Rex Dieter wrote:
> Jeff Sheltren wrote:
>
>> On Fri, Oct 31, 2014 at 5:42 AM, Rex Dieter
>> wrote:
>>
>>> Rex Dieter wrote:
>>>
>>> > +%epel %{?rhel}%{!?:rhel:7}
>>>
>>> typo alert ^^ (in the second part), but hopefully you get the idea.
>>>
>>> Or, if you'd rath
Jeff Sheltren wrote:
> On Fri, Oct 31, 2014 at 5:42 AM, Rex Dieter
> wrote:
>
>> Rex Dieter wrote:
>>
>> > +%epel %{?rhel}%{!?:rhel:7}
>>
>> typo alert ^^ (in the second part), but hopefully you get the idea.
>>
>> Or, if you'd rather not depend on %rhel macro, and just hard-code to 7,
>> that
>
On Fri, Oct 31, 2014 at 5:42 AM, Rex Dieter wrote:
> Rex Dieter wrote:
>
> > +%epel %{?rhel}%{!?:rhel:7}
>
> typo alert ^^ (in the second part), but hopefully you get the idea.
>
> Or, if you'd rather not depend on %rhel macro, and just hard-code to 7,
> that
> would be fine too.
>
The approach
Rex Dieter wrote:
> +%epel %{?rhel}%{!?:rhel:7}
typo alert ^^ (in the second part), but hopefully you get the idea.
Or, if you'd rather not depend on %rhel macro, and just hard-code to 7, that
would be fine too.
-- Rex
___
epel-devel mailing list
ep
Rex Dieter wrote:
> Rex Dieter wrote on Oct 16:
>
>> I'd like to be able to conditionalize some package features depending on
>> if
>> epel repo is enabled or not. One way to accomplish that goal is if epel-
>> release defined some macro, say, something like %{epel}, similar to
>> %{feodra} or %
Rex Dieter wrote:
> I'd like to be able to conditionalize some package features depending on
> if
> epel repo is enabled or not. One way to accomplish that goal is if epel-
> release defined some macro, say, something like %{epel}, similar to
> %{feodra} or %{rhel}
>
> (I don't care what the mac
Chuck Anderson wrote:
> On Mon, Oct 20, 2014 at 08:56:35PM -0500, Rex Dieter wrote:
>> Jeff Sheltren wrote:
>>
>> > On Mon, Oct 20, 2014 at 3:11 PM, Rex Dieter
>> > wrote:
>> >>
>> >>
>> >> ping, any comment or objection?
>> >>
>> >> I'll work on a patch for epel-release to implement a %{epel} m
On Mon, Oct 20, 2014 at 08:56:35PM -0500, Rex Dieter wrote:
> Jeff Sheltren wrote:
>
> > On Mon, Oct 20, 2014 at 3:11 PM, Rex Dieter
> > wrote:
> >>
> >>
> >> ping, any comment or objection?
> >>
> >> I'll work on a patch for epel-release to implement a %{epel} macro, in
> >> case anyone was wait
Jeff Sheltren wrote:
> On Mon, Oct 20, 2014 at 3:11 PM, Rex Dieter
> wrote:
>>
>>
>> ping, any comment or objection?
>>
>> I'll work on a patch for epel-release to implement a %{epel} macro, in
>> case anyone was waiting for implementation details.
>>
>>
> Seems like it can't hurt much to have su
On Mon, Oct 20, 2014 at 3:11 PM, Rex Dieter wrote:
>
>
> ping, any comment or objection?
>
> I'll work on a patch for epel-release to implement a %{epel} macro, in case
> anyone was waiting for implementation details.
>
>
Seems like it can't hurt much to have such a macro defined by the
epel-relea
Rex Dieter wrote on Oct 16:
> I'd like to be able to conditionalize some package features depending on
> if
> epel repo is enabled or not. One way to accomplish that goal is if epel-
> release defined some macro, say, something like %{epel}, similar to
> %{feodra} or %{rhel}
>
> (I don't care wh
I'd like to be able to conditionalize some package features depending on if
epel repo is enabled or not. One way to accomplish that goal is if epel-
release defined some macro, say, something like %{epel}, similar to
%{feodra} or %{rhel}
(I don't care what the macro is named, as long as the bik
16 matches
Mail list logo
