From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-sparc@lists.gentoo.org
Subject: Re: [gentoo-sparc] Re: Official SPARC64 Port
Date: Thu, 28 Jan 2016 18:46:13 -0500 [thread overview]
Message-ID: <20160128234613.GI14840@vapier.lan> (raw)
In-Reply-To: <56AAA62C.1040908@triadic.us>
[-- Attachment #1: Type: text/plain, Size: 971 bytes --]
On 28 Jan 2016 18:37, Alex McWhirter wrote:
> On 01/28/2016 06:26 PM, Mike Frysinger wrote:
> > you don't have to be a dev to get your work merged. you just have to
> > be a dev to do the final push yourself. so if you have changes that
> > you think are ready to go now, we can get them merged.
>
> I want to do a bit more testing to ensure im not going to break any
> existing sparc32 installs. I am fairly certain that we are going to
> break sparc32 + multilib, but considering that profile was never
> officially released it may not be that big of a deal.
>
> My main concern with sparc32 + multilib is what happens when you have
> system installed with SYMLINK_LIB="yes" and later change it to "no".
the profile is explicitly labeled "experimental":
default/linux/sparc/experimental/multilib
so just deleting it and forcing the people (if any) to manually update
is fine. you don't run "experimental" on a system in production ;).
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-01-28 23:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 23:06 [gentoo-sparc] Official SPARC64 Port Alex McWhirter
2016-01-28 23:26 ` [gentoo-sparc] " Mike Frysinger
2016-01-28 23:37 ` Alex McWhirter
2016-01-28 23:46 ` Mike Frysinger [this message]
2016-01-30 0:28 ` [gentoo-sparc] " Alex McWhirter
2016-01-30 0:44 ` Mike Frysinger
2016-01-30 0:55 ` Alex McWhirter
2016-02-01 9:24 ` Alex McWhirter
2016-02-01 17:44 ` Mike Frysinger
2016-02-01 19:29 ` Alex McWhirter
2016-02-01 20:24 ` Mike Frysinger
2016-02-01 20:34 ` Alex McWhirter
2016-02-01 20:51 ` Mike Frysinger
2016-02-01 22:03 ` Alex McWhirter
2016-02-04 18:40 ` Alex McWhirter
2016-02-04 21:54 ` Mike Frysinger
2016-02-04 23:44 ` Alex McWhirter
2016-02-07 10:35 ` Alex McWhirter
2016-02-08 15:21 ` Mike Frysinger
2016-02-08 20:48 ` Alex McWhirter
2016-02-09 5:11 ` Alex McWhirter
2016-02-09 6:14 ` Mike Frysinger
2016-02-13 9:26 ` Alex McWhirter
2016-02-13 11:25 ` Mike Frysinger
2016-02-13 17:32 ` Alex McWhirter
2016-02-13 21:26 ` Alex McWhirter
2016-02-14 0:44 ` Mike Frysinger
2016-02-14 23:44 ` Alex McWhirter
2016-02-15 2:13 ` Mike Frysinger
2016-02-17 22:11 ` Alex McWhirter
2016-02-17 22:46 ` Mike Frysinger
2016-02-17 22:52 ` Alex McWhirter
2016-02-19 8:37 ` Alex McWhirter
2016-03-11 3:53 ` Alex McWhirter
2016-08-08 22:52 ` Jack Morgan
2016-08-09 5:14 ` alexmcwhirter
2016-08-10 18:45 ` Jack Morgan
2016-08-31 17:26 ` alexmcwhirter
2016-09-01 0:46 ` Jack Morgan
2016-09-04 19:27 ` [gentoo-sparc] -fPIC vs -fpic = Headaches alexmcwhirter
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=20160128234613.GI14840@vapier.lan \
--to=vapier@gentoo.org \
--cc=gentoo-sparc@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