public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: James <wireless@tampabay.rr.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: blockage
Date: Mon, 23 Mar 2015 22:07:31 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150323T213533-115@post.gmane.org> (raw)
In-Reply-To: 550FE3FB.4010007@gmail.com

Alan McKinnon <alan.mckinnon <at> gmail.com> writes:

> > Sounds like you're volunteering, Alan.   
> I do have some of the required skills, and I have free time right now.

Ah; stepping up are we? I'll be hoping you are taking requests on
the 'portage thingy' ? 
How'z about extending emerge with a few extra commands & operands :: ?

that installs a new gentoo system (image) via an ansible file(s)?
Stephan put some stuff up a while back, but I have not gotten
back around to testing it. I recall you had some early workings too?

There's even some open source work on an ansible gui [1]:


If we have some quick way to install, then systems could be setup,
customized, used for testing and torn down again, all in a few hours? I'd
focus on simple, minimized installs and it would give the user base a way to
duplicate  systems for problem verification and resolution. Also, as
clusters, clouds and various virtualizations continue to mature, it could
also aid in other forms of gentoo image debugging and verification
if bugs exist only in virtualized form or also in traditional installs.

Just a few thoughts; no big deal. If you step back a bit there are 
many ways to approach portage/ebuild enhancements.



> Maybe I'll have a deeper look into portage's code with a view to
> improving this area. No promises thought 

The dev repos and project repos  are good places to start [2,3]:


James

[1] https://github.com/ansible-semaphore/semaphore

[2] http://gitweb.gentoo.org/

[3] http://gitweb.gentoo.org/proj/




  parent reply	other threads:[~2015-03-23 22:08 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-22  3:24 [gentoo-user] blockage lee
2015-03-22  5:21 ` [gentoo-user] blockage Jonathan Callen
2015-03-22 11:00   ` lee
2015-03-22  9:24 ` [gentoo-user] blockage Alan McKinnon
2015-03-22 10:45   ` lee
2015-03-22 11:31     ` Alan McKinnon
2015-03-22 12:09       ` Tom H
2015-03-22 13:04         ` lee
2015-03-22 15:02           ` [gentoo-user] blockage Jonathan Callen
2015-03-22 18:08             ` lee
2015-03-22 21:22               ` Alan McKinnon
2015-03-22 21:54                 ` Dale
2015-03-23  9:55                 ` Peter Humphrey
2015-03-23  9:59                   ` Alan McKinnon
2015-03-23 10:04                     ` Peter Humphrey
2015-03-23 22:07                     ` James [this message]
2015-03-28 13:44                       ` lee

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=loom.20150323T213533-115@post.gmane.org \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-user@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