From: Shinkan <shinkan@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Cross Dev Tricks + Hardened questions
Date: Wed, 2 Dec 2009 10:28:39 +0100 [thread overview]
Message-ID: <166af1cf0912020128h6db07df0v93897d6694aa563@mail.gmail.com> (raw)
In-Reply-To: <20091202001733.25376.qmail@stuge.se>
[-- Attachment #1: Type: text/plain, Size: 905 bytes --]
2009/12/2 Peter Stuge <peter@stuge.se>
> It's much less rigid is the point I guess. catalyst has some behavior
> set by python code in /usr/lib and if you change that a lot then
> metro might be a lot better I guess.
>
I think a distro-world based build tool shouldn't be "changed a lot" because
it must at start simplify everything the base distro can do.
Talking about Gentoo, as we can do almost everything, the build tool should
just make "doing everything" easier.
Moreover, what about taking a tool dedicated to another distro (strongly
related in this case, I bet) to work with our distro which already have a
tool ?!
Wouldn't be more clever to start enhancing catalyst to meet special needs
and submit that to devs ?
--
Pierre.
"Sometimes when I'm talking, my words can't keep up with my thoughts. I
wonder why we think faster than we speak. Probably so we can think twice." -
Bill Watterson
[-- Attachment #2: Type: text/html, Size: 1279 bytes --]
next prev parent reply other threads:[~2009-12-02 10:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 18:24 [gentoo-embedded] Cross Dev Tricks + Hardened questions Shinkan
2009-11-30 21:12 ` Peter Stuge
2009-12-01 8:44 ` Shinkan
2009-12-01 17:48 ` Ned Ludd
2009-12-01 19:03 ` Ed W
2009-12-01 20:51 ` Peter Stuge
2009-12-01 22:24 ` Shinkan
2009-12-02 0:17 ` Peter Stuge
2009-12-02 9:28 ` Shinkan [this message]
2009-12-01 19:03 ` Peter Stuge
2009-12-01 20:52 ` Shinkan
2009-12-01 23:57 ` Peter Stuge
2009-12-02 8:02 ` [OT] Catalyst, was: " Eckard Brauer
2009-12-02 9:04 ` Ed W
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=166af1cf0912020128h6db07df0v93897d6694aa563@mail.gmail.com \
--to=shinkan@gmail.com \
--cc=gentoo-embedded@lists.gentoo.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