Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe-meta-systemd 4/5] pointercal-xinput: remove
Date: Wed, 6 Feb 2013 16:25:29 +0100	[thread overview]
Message-ID: <20130206152529.GA3271@jama> (raw)
In-Reply-To: <CALbNGRR9isWgLJmRL3thvhkFhirwLR2YqoXfrHPtgMqOHrYQBw@mail.gmail.com>

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

On Wed, Feb 06, 2013 at 04:12:50PM +0100, Andreas Müller wrote:
> On Wed, Feb 6, 2013 at 3:48 PM, Martin Jansa <martin.jansa@gmail.com> wrote:
> > On Tue, Feb 05, 2013 at 11:18:42PM +0100, Andreas Müller wrote:
> >> Calibration values are stored now in /etc/xorg.conf.d/99-<device>.conf. After
> >
> > So the plan to replace pointercal-xinput in BSP layers
> > is to convert pointercal.xinput files to 99-<device>.conf files provided
> > by xserver-xf86-conf bbappend?
> I would have appended it to xinput-calibrator because that's where the
> configuration files are used. I can put them also to xserver-xf86-conf
> bbappend - have no strong opinion here.

xinput-calibrator does not need to be MACHINE_ARCH, that's why they were
in separate pointercal-xinput before.

xserver-xf86-config on other hand is usually MACHINE_ARCH so it would be
better to add them there.

Or create new recipe for them and RDEPEND it from xinput-calibrator...

> > And do you have some script to convert them or do you convert them
> > manually?
> >
> I wanted to convert them manually but a script is more reliable - will
> do that next week.
> 
> Andreas
> 
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

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

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

  reply	other threads:[~2013-02-06 15:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-05 22:18 [meta-oe-meta-systemd 0/5] xinput-calibrator rework Andreas Müller
2013-02-05 22:18 ` [meta-oe-meta-systemd 1/5] xinput-calibrator: update to latest git commit Andreas Müller
2013-02-05 22:18 ` [meta-oe-meta-systemd 2/5] xinput-calibrator: Add --output-filename to store calibration to file Andreas Müller
2013-02-05 22:18 ` [meta-oe-meta-systemd 3/5] xinput-calibrator: rework Andreas Müller
2013-02-05 22:18 ` [meta-oe-meta-systemd 4/5] pointercal-xinput: remove Andreas Müller
2013-02-06 14:48   ` Martin Jansa
2013-02-06 15:12     ` Andreas Müller
2013-02-06 15:25       ` Martin Jansa [this message]
2013-02-06 15:45         ` Andreas Müller
2013-02-07 10:01   ` Koen Kooi
2013-02-08 22:11     ` Andreas Müller
2013-02-05 22:18 ` [meta-oe-meta-systemd 5/5] xinput-calibrator: do not RDEPEND xterm Andreas Müller
2013-02-07 10:08   ` Koen Kooi
2013-02-07 10:06 ` [meta-oe-meta-systemd 0/5] xinput-calibrator rework Koen Kooi
2013-02-08 22:10   ` Andreas Müller
2013-02-14  9:41     ` Andreas Müller

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=20130206152529.GA3271@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox