All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-qt5][PATCH v2 05/11] qt5: disable debian auto renaming
Date: Wed, 2 Sep 2015 19:25:25 +0200	[thread overview]
Message-ID: <20150902172525.GE2470@jama> (raw)
In-Reply-To: <CAP9ODKoUVXp5MuOiTTiYQfkWzWjU=wf7dKVpNnBJW2KNudZZyA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]

On Wed, Sep 02, 2015 at 02:07:15PM -0300, Otavio Salvador wrote:
> On Tue, Aug 25, 2015 at 8:43 AM, Samuli Piippo
> <samuli.piippo@theqtcompany.com> wrote:
> > Some of the Qt modules have multiple libs, which prevents debian auto
> > renaming to work correctly. Instead of only having some modules renamed,
> > disable renaming for all Qt module packages, so that all they all are
> > named as ${PN}.

I don't think this explanation is good enough reason to disable debian
renaming and that's why I didn't take it into master-next yet.

The original idea was to let qt5 package with libraries coexist with qt4
ones, I agree that not many people are using this, but on the other hand
few people asked me to provide more granular packages for qt5, so
instead of disabling debian rename everywhere why don't we split the
packages with multiple libs or define LEAD_SONAME where one library is
significantly more important than the rest and the package should be
named after it?

Regards,

> >
> > Signed-off-by: Samuli Piippo <samuli.piippo@theqtcompany.com>
> 
> I think you could rework this to use a python function to set it for
> all the packages and ease long term maintenance.
> 
> -- 
> Otavio Salvador                             O.S. Systems
> http://www.ossystems.com.br        http://code.ossystems.com.br
> Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750
> -- 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2015-09-02 17:25 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 11:43 [meta-qt5][PATCH v2 00/11] upstreaming Qt for Device Creation changes Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 01/11] qt5: make populate_sdk_qt5 reusable Samuli Piippo
2015-08-30 12:49   ` Jonathan Liu
2015-09-01 13:21     ` Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 02/11] qt5: improve Qt module package handling Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 03/11] qt5: improve support for native and nativesdk modules Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 04/11] qt5: add host paths to qt.conf Samuli Piippo
2015-08-30 12:30   ` Jonathan Liu
2015-09-01 13:07     ` Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 05/11] qt5: disable debian auto renaming Samuli Piippo
2015-09-02 17:07   ` Otavio Salvador
2015-09-02 17:25     ` Martin Jansa [this message]
2015-09-02 17:53       ` Otavio Salvador
2015-09-03 13:10         ` Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 06/11] qt5: make qt5.inc reusable qt5-module.bbclass Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 07/11] qttools: use one recipe for all compilations Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 08/11] qtbase: remove dependency to sqlite Samuli Piippo
2015-09-02 17:08   ` Otavio Salvador
2015-08-25 11:43 ` [meta-qt5][PATCH v2 09/11] qtbase: PACKAGECONFIGs for libproxy and libinput Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 10/11] qtlocation: use correct dependencies Samuli Piippo
2015-08-25 11:43 ` [meta-qt5][PATCH v2 11/11] qtwebengine: fix problem with recursive qmake call Samuli Piippo

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=20150902172525.GE2470@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.