netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Machata <petrm@nvidia.com>
To: <aclaudi@redhat.com>
Cc: Petr Machata <petrm@nvidia.com>, <luca.boccassi@gmail.com>,
	<netdev@vger.kernel.org>, <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2] Revert "Makefile: ensure CONF_USR_DIR honours the libdir config"
Date: Fri, 10 Nov 2023 14:54:16 +0100	[thread overview]
Message-ID: <87bkc1yaqa.fsf@nvidia.com> (raw)
In-Reply-To: <87fs1dyax9.fsf@nvidia.com>


Petr Machata <petrm@nvidia.com> writes:

> luca.boccassi@gmail.com writes:
>
>> From: Luca Boccassi <bluca@debian.org>
>>
>> LIBDIR in Debian and derivatives is not /usr/lib/, it's
>> /usr/lib/<architecture triplet>/, which is different, and it's the
>> wrong location where to install architecture-independent default
>> configuration files, which should always go to /usr/lib/ instead.
>> Installing these files to the per-architecture directory is not
>> the right thing, hence revert the change.
>
> So I looked into the Fedora package. Up until recently, the files were
> in /etc, but it seems there was a deliberate change in the spec file
> this September that moved them to /usr/lib or /usr/lib64.
>
> Luca -- since you both sent the patch under reversion, and are Fedora

Ugh, I mean Andrea, not Luca. Sorry!

> maintainer, could you please elaborate on what the logic was behind it?
> It does look odd to me to put config files into an arch-dependent
> directory, but I've been out of packaging for close to a decade at this
> point.

  reply	other threads:[~2023-11-10 13:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06  0:14 [PATCH iproute2] Revert "Makefile: ensure CONF_USR_DIR honours the libdir config" luca.boccassi
2023-11-10 13:34 ` Petr Machata
2023-11-10 13:54   ` Petr Machata [this message]
2023-11-10 20:31     ` Andrea Claudi
2023-11-10 22:01       ` Luca Boccassi
2023-11-10 13:54   ` Luca Boccassi
2023-11-13 16:40 ` patchwork-bot+netdevbpf
2023-11-13 18:12   ` Andrea Claudi
2023-11-13 23:38     ` Stephen Hemminger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bkc1yaqa.fsf@nvidia.com \
    --to=petrm@nvidia.com \
    --cc=aclaudi@redhat.com \
    --cc=luca.boccassi@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).