From: Enrico Scholz <enrico.scholz@sigma-chemnitz.de>
To: openembedded-core@lists.openembedded.org
Subject: Re: RFE: make the init manager an image feature (again)
Date: Mon, 25 Feb 2013 11:28:22 +0100 [thread overview]
Message-ID: <lyr4k43cxl.fsf@ensc-virt.intern.sigma-chemnitz.de> (raw)
In-Reply-To: <20130224085046.GF3154@sakrah.homelinux.org> (Khem Raj's message of "Sun, 24 Feb 2013 00:50:48 -0800")
Khem Raj <raj.khem-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
>> > On the specifics of the do_install_append, you've seen my comments about
>> > how we're not learning from past mistakes with the way the do_install in
>> > the class was written. I note Phil also agreed with them, both of us
>> > remembering some of the horrors we've dealt with in the past (and
>> > binconfig.bbclass is still around, sadly).
>>
>> So you prefer same code to copy same type of files all over the recipes?
>
> duplicating usecase is better even though it may sound copying here
> now think if you add this to a bbclass and works ok for a package
> where we glue the unitfiles fast forward 6mos and the next version of
> the package has added the unitfiles into the package itself since
> systemd is so cool. We will be silently installing our own unit files
> without knowing.
The recent .bbappends with their own do_install_append have this problem
too. But due to the code replication the problem must be fixed at a lot
of different places instead of at a central one.
The .bbclass can do some sanity checks (e.g. making the copy operation
fail when the unit file already exists).
> Worst if the files from package are different. Having individual
> install append gives you an opportunity to this append
I do not see how this is better than removing the local .service from
SRC_URI.
Enrico
next prev parent reply other threads:[~2013-02-25 10:45 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-15 18:19 RFE: make the init manager an image feature (again) Enrico Scholz
2013-02-15 18:47 ` Otavio Salvador
2013-02-15 23:44 ` Martin Jansa
2013-02-16 9:15 ` Richard Purdie
2013-02-16 10:47 ` Otavio Salvador
2013-02-16 12:53 ` Richard Purdie
2013-02-16 13:41 ` Otavio Salvador
2013-02-24 8:50 ` Khem Raj
2013-02-24 14:10 ` Otavio Salvador
2013-02-25 10:28 ` Enrico Scholz [this message]
2013-02-17 23:20 ` Martin Jansa
2013-02-18 10:17 ` Enrico Scholz
2013-02-20 19:58 ` Burton, Ross
2013-02-21 10:34 ` Enrico Scholz
2013-02-21 10:40 ` Burton, Ross
2013-02-21 11:34 ` Enrico Scholz
2013-02-21 11:50 ` Otavio Salvador
2013-02-21 12:01 ` Phil Blundell
2013-02-16 11:57 ` Enrico Scholz
2013-02-16 12:34 ` Richard Purdie
2013-02-16 13:28 ` Otavio Salvador
2013-02-16 19:40 ` Martin Jansa
2013-02-16 19:49 ` Otavio Salvador
2013-02-17 13:06 ` Enrico Scholz
2013-02-21 15:35 ` Burton, Ross
2013-02-21 15:49 ` Otavio Salvador
2013-02-21 17:20 ` Enrico Scholz
2013-02-24 10:37 ` Ross Burton
2013-02-24 10:45 ` Ross Burton
2013-02-24 14:06 ` Otavio Salvador
2013-02-24 22:04 ` Ross Burton
2013-02-25 7:38 ` Martin Jansa
2013-02-25 7:46 ` Andreas Müller
2013-02-25 11:45 ` Otavio Salvador
2013-02-25 11:28 ` Enrico Scholz
2013-02-26 6:45 ` Khem Raj
-- strict thread matches above, loose matches on Subject: below --
2013-02-16 20:20 Daniel Lazzari
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=lyr4k43cxl.fsf@ensc-virt.intern.sigma-chemnitz.de \
--to=enrico.scholz@sigma-chemnitz.de \
--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