public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Forrest Voight <voights@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Player, Stage, Gazebo eBuilds
Date: Wed, 31 Aug 2005 21:22:34 +0000	[thread overview]
Message-ID: <b572c9e1050831142240852dfa@mail.gmail.com> (raw)
In-Reply-To: <e7963922050831140617b7084a@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1604 bytes --]

If you want to you can test it. I still have some dependency issues
with player/stage. This is a standalone program.

You can test it by running:
wxgazebo /usr/share/gazebo/worlds/example.world

Look at that directory and try out the other worlds if you want to.

Thanks,
Forrest

On 8/31/05, Stefan Schweizer <genstef@gentoo.org> wrote:
> On 8/31/05, Ciaran McCreesh <ciaranm@gentoo.org> wrote:
> > On Wed, 31 Aug 2005 20:36:03 +0000 Forrest Voight <voights@gmail.com>
> > wrote:
> > | Is it possible for me to mantain the packages?
> > 
> > We don't (or at least shouldn't...) give out CVS to people just for a
> > few ebuilds. If you contribute a lot of high quality stuff then someone
> > may offer to mentor you.
> 
> So what iss the alternative? maintainer-wanted@ is really
> unsatisfactory for people that want to contribute. Do you think
> someone will just commit all his work?
> 
> I think we should either give cvs access to everyone who wants to
> contribute or define some standard way where developers can review
> contributed ebuilds and fix them so that they can get into portage
> easily. And actualy get into portage or some kind of repo and not the
> bugzilla.
> 
> But as defining new ways to distribute/review ebuilds is not so easy I
> think it is atm best to let everyone take the quizes and use cvs who
> wants to contribute ebuilds to gentoo.
> 
> So who wants to mentro him? :)
> 
> Forrest, where are the ebuilds anyway so that we can have a look at them?
> 
> Regards,
> Stefan
> 
> -- 
> gentoo-dev@gentoo.org mailing list
> 
>

[-- Attachment #2: gazebo.tar --]
[-- Type: application/x-tar, Size: 10240 bytes --]

  parent reply	other threads:[~2005-08-31 21:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31 13:42 [gentoo-dev] New developer: Stefaan De Roeck (stefaan) Tom Martin
2005-08-31 14:27 ` Maurice van der Pot
2005-08-31 15:33 ` Ciaran McCreesh
2005-08-31 18:04 ` Michael Kohl
2005-08-31 20:13   ` [gentoo-dev] Player, Stage, Gazebo eBuilds Forrest Voight
2005-08-31 20:17     ` Dan Meltzer
2005-08-31 20:18     ` Joshua Baergen
2005-08-31 20:36       ` [gentoo-dev] " Forrest Voight
2005-08-31 20:43         ` Ciaran McCreesh
2005-08-31 20:53           ` Forrest Voight
2005-08-31 21:02             ` Ciaran McCreesh
2005-08-31 21:06           ` Stefan Schweizer
2005-08-31 21:22             ` Ciaran McCreesh
2005-08-31 21:22             ` Forrest Voight [this message]
2005-08-31 21:41               ` Ciaran McCreesh
2005-09-01 12:07           ` Dmitry Lukashin

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=b572c9e1050831142240852dfa@mail.gmail.com \
    --to=voights@gmail.com \
    --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