From: "\"Paweł Hajdan, Jr.\"" <phajdan.jr@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: Last rites: www-client/chromium-bin
Date: Thu, 10 Mar 2011 12:12:08 +0100 [thread overview]
Message-ID: <4D78B208.9060409@gentoo.org> (raw)
In-Reply-To: <pan.2011.03.05.10.05.49@cox.net>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
On 3/5/11 11:05 AM, Duncan wrote:
> What about handling chromium-bin the same way amd64 handles grub-static?
> They create a standard binpkg of the normal grub ebuild (using
> standardized USE flags, of course), using that as the source tarball for
> the grub-static ebuild, which then simply ebuild-scripts the unpack and
> install of the binpkg tarball.
That's the chromium-bin, really. The difference is that chromium has
more deps and takes more time to compile than grub. Also, it has much
more frequent releases, and almost every stable release is a security
update.
> In theory, the ebuild could even grab and merge the appropriate binpkg
> based on arch, allowing the ebuild to be keyworded for more archs than the
> usual binary-only ebuild tends to be, altho I'm not sure that'd work in
> practice as I'm unsure of the effects on the metadata cache and whether
> that would be allowed or not.
Yeah, I can understand how it could work technically. The only issue is
to make the version bump one automated step.
Paweł Hajdan, Jr.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2011-03-10 11:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 9:35 [gentoo-dev] Last rites: www-client/chromium-bin "Paweł Hajdan, Jr."
2011-03-04 23:32 ` Tomáš Chvátal
2011-03-04 23:46 ` Alex Alexander
2011-03-04 23:51 ` Tomáš Chvátal
2011-03-04 23:58 ` Alex Alexander
2011-03-05 9:23 ` "Paweł Hajdan, Jr."
2011-03-05 10:05 ` [gentoo-dev] " Duncan
2011-03-10 11:12 ` "Paweł Hajdan, Jr." [this message]
2011-03-10 20:04 ` James Cloos
2011-03-10 20:33 ` Mike Gilbert
2011-03-10 20:42 ` "Paweł Hajdan, Jr."
2011-03-11 22:17 ` James Cloos
2011-03-05 2:33 ` [gentoo-dev] " Antoni Grzymala
2011-03-05 2:41 ` Rich Freeman
2011-03-05 3:01 ` dev-random
2011-03-05 8:01 ` Jeroen Roovers
2011-03-05 10:00 ` [gentoo-dev] " Nikos Chantziaras
2011-03-05 10:05 ` Nikos Chantziaras
2011-03-05 10:21 ` Dale
2011-03-05 10:41 ` Rich Freeman
2011-03-05 10:29 ` Rich Freeman
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=4D78B208.9060409@gentoo.org \
--to=phajdan.jr@gentoo.org \
--cc=gentoo-dev@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