From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] What's up with the kernel names? (Again)
Date: Fri, 6 Feb 2009 10:06:29 +0100 [thread overview]
Message-ID: <A56AD9EF90944EFB93E86E3692353870@aeglos> (raw)
In-Reply-To: 871vucar1o.fsf@macbook.be.48ers.dk
>>>>> "Ulf" == Ulf Samuelsson <ulf.samuelsson@atmel.com> writes:
Ulf> ?The AT91 uboot patches and autoscripts rely on this very exact
naming,
Ulf> so if you commit your patch, you break the at91 support.
So they are broken for people using the simple linux build already?
==> The previous default was to use the advanced build, if my memory
does not fail me.
If you use a simple build then you do not get any help from the
autoscript.
Ulf> If you add KERNEL_VERSION to the root fs name you do things
Ulf> automatically, if you dont then everything is manually, and you
Ulf> have a risk of mismatch between name and actual version. I
Ulf> would not mind that the rootfs contains kernel version, but it
Ulf> will break the at91 u-boot autoscripts which means that it
Ulf> should avoided at this point, and introduced in a future
Ulf> buildroot.
Ulf> To avoid bugs due to people forgetting to update onfig the kernel name
Ulf> needs to depend BOTH on PROJECT and LINUX_VERSION.
Then set prefix/suffix.
==> How can setting prefix/suffix retroactively help people that has
forgotten
to set prefix/suffix?
>> The $(DATE) seams to be default to rootfs suffix already, all you have
>> to do is change it per project to include the project or board name.
Ulf> I think your major problem is that the DATE changes.
Ulf> I think it is fair to allow DATE to be in the rootfs suffix.
Sure, setting prefix/suffix to $(DATE) should work - But it shouldn't
be default.
Ulf> but I still think your needs are best accomodated by
Ulf> ln -s $(LINUX_KERNEL_NAME) uImage
No, lets not add any more clutter to binaries/
==> If you do not like that solution, then letting people that
want uImage , build the simple linux would work for me.
But your opinion seems to be that you want to do things
in a certain way, and you want to ensure that noone
can do it in a different way, regardless if their use case
is different from yours.
--
Bye, Peter Korsgaard
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2009-02-06 9:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 1:49 [Buildroot] What's up with the kernel names? (Again) Thiago A. Corrêa
2009-02-04 7:39 ` Peter Korsgaard
2009-02-04 12:29 ` Peter Korsgaard
2009-02-05 2:33 ` Thiago A. Corrêa
2009-02-05 13:23 ` Peter Korsgaard
2009-02-05 20:37 ` Ulf Samuelsson
2009-02-06 2:28 ` Thiago A. Corrêa
2009-02-06 6:16 ` Ulf Samuelsson
2009-02-06 8:49 ` Peter Korsgaard
2009-02-06 9:06 ` Ulf Samuelsson [this message]
2009-02-06 12:30 ` Peter Korsgaard
2009-02-06 8:45 ` Peter Korsgaard
2009-02-06 8:58 ` Ulf Samuelsson
2009-02-06 8:44 ` Peter Korsgaard
2009-02-05 20:23 ` Ulf Samuelsson
2009-02-06 8:41 ` Peter Korsgaard
2009-02-06 8:56 ` Ulf Samuelsson
2009-02-06 12:27 ` Peter Korsgaard
2009-02-06 14:31 ` Thiago A. Corrêa
2009-02-06 15:18 ` Thiago A. Corrêa
2009-02-09 17:24 ` Ulf Samuelsson
2009-02-09 19:34 ` Peter Korsgaard
2009-02-09 22:52 ` Ulf Samuelsson
2009-02-10 1:25 ` Thiago A. Corrêa
2009-02-10 8:02 ` Ulf Samuelsson
2009-02-10 9:28 ` Peter Korsgaard
2009-02-10 10:32 ` Ulf Samuelsson
2009-02-10 9:17 ` Peter Korsgaard
2009-02-10 10:16 ` Ulf Samuelsson
2009-02-10 12:51 ` Peter Korsgaard
2009-02-10 13:50 ` Ulf Samuelsson
2009-02-10 16:34 ` Thiago A. Corrêa
2009-02-10 17:17 ` Thiago A. Corrêa
2009-02-10 17:42 ` Ulf Samuelsson
2009-02-10 18:48 ` Thiago A. Corrêa
2009-02-11 20:03 ` Ulf Samuelsson
2009-02-11 20:15 ` Peter Korsgaard
2009-02-12 18:16 ` Ulf Samuelsson
2009-02-16 22:21 ` Thiago A. Corrêa
2009-02-17 11:26 ` Peter Korsgaard
2009-02-10 18:26 ` Ulf Samuelsson
2009-02-10 18:50 ` Ulf Samuelsson
2009-02-10 20:06 ` Thiago A. Corrêa
2009-02-10 18:59 ` Ulf Samuelsson
2009-02-10 19:49 ` Ulf Samuelsson
2009-02-10 20:06 ` Peter Korsgaard
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=A56AD9EF90944EFB93E86E3692353870@aeglos \
--to=ulf.samuelsson@atmel.com \
--cc=buildroot@busybox.net \
/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