From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: RFC: Making it mandantory to have a checksums.ini entry
Date: Tue, 30 Sep 2008 23:58:24 -0300 [thread overview]
Message-ID: <87y719nhrj.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <200810010447.44667.zecke@selfish.org> (Holger Freyther's message of "Wed\, 1 Oct 2008 04\:47\:41 +0200")
Holger Freyther <zecke@selfish.org> writes:
> The spend time on copy and pasting a checksums.ini entry is really small and
> the value is very high. Stuff like macports is forcing one to have checksums
> as well.
This makes a lot of sense for me since the way it is being used
currently makes no sense.
If people has internal repositories that don't want to use checksum it
can be allowed by recipe basis as you already support in your proposed
patch.
+1
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: otavio@debian.org UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
next prev parent reply other threads:[~2008-10-01 3:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-01 2:47 RFC: Making it mandantory to have a checksums.ini entry Holger Freyther
2008-10-01 2:58 ` Otavio Salvador [this message]
2008-10-01 7:06 ` Koen Kooi
2008-10-15 17:34 ` Holger Freyther
2008-10-15 17:51 ` Koen Kooi
2008-10-15 18:17 ` Marcin Juszkiewicz
2008-10-16 12:20 ` Sledz, Steffen
2008-10-16 12:39 ` Thomas Kunze
2008-10-16 12:44 ` Sledz, Steffen
2008-10-16 12:52 ` Thomas Kunze
2008-10-16 13:12 ` Sledz, Steffen
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=87y719nhrj.fsf@neumann.lab.ossystems.com.br \
--to=otavio@debian.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.