Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
Subject: Re: [PATCH] xrandr: update to 1.5.1
Date: Tue, 13 Aug 2019 23:44:42 +0300	[thread overview]
Message-ID: <20190813204442.GA15311@localhost> (raw)
In-Reply-To: <CANNYZj8iGTPsJ9jJL70o9xfs2JKAikWrxtbmoBB_xQ-ZLMkzqw@mail.gmail.com>

On Tue, Aug 13, 2019 at 10:01:25PM +0200, Alexander Kanavin wrote:
> On Tue, 13 Aug 2019 at 21:53, Oleksandr Kravchuk <
> open.source@oleksandr-kravchuk.com> wrote:
> 
> > SRC_URI was moved from xorg-app-common.inc, since it has hardcoded file
> > extension (tar.bz2), but upstream stopped publishing tar.bz2 archives
> > for newer versions of the packages.
> >
> 
> Should this be rather fixed in the common include though? I took a brief
> look here:
> https://www.x.org/releases/individual/app/
> and it seems like we can switch to xz for everything or almost everything
> without much pain.

If there end up several compression types here this could be made 
configurable, similar to GNOME_COMPRESS_TYPE.

> Alex

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



      parent reply	other threads:[~2019-08-13 20:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-13 19:52 [PATCH] xrandr: update to 1.5.1 Oleksandr Kravchuk
2019-08-13 20:01 ` Alexander Kanavin
2019-08-13 20:03   ` Alexander Kanavin
2019-08-13 20:44   ` Adrian Bunk [this message]

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=20190813204442.GA15311@localhost \
    --to=bunk@stusta.de \
    --cc=alex.kanavin@gmail.com \
    --cc=open.source@oleksandr-kravchuk.com \
    --cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox