From: George Shapovalov <georges@its.caltech.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Unstable branch proposal - second round
Date: Sat, 16 Mar 2002 17:04:26 -0800 [thread overview]
Message-ID: <200203170100.RAA29588@chamber.cco.caltech.edu> (raw)
In-Reply-To: <5.1.0.14.2.20020416180627.02c7eeb0@mail.cybrains.net>
Well, the main idea I try to put up here is to expose new ebuilds as much as
possible by pushing ALL submissions to the portage tree for people who want
to see what's up on the table, while maintaining only the stable core access
for people who only need thoroughly tested stuff.
If something can be easily setup to simplify ebuild submission process this
is fine and in fact does not change much the idea. bugs.gentoo.org is pretty
simple IMHO, and majority of users are developers, while as far as I can tell
linux newcomers are not uncommon to gentoo either.
Please see my new post for clarification. In short I feel that it is
necessary to introduce multiple ebuild-state levels to better represent the
"real-world life of a package", which will also help end-users to follow the
stock and contribute to what he feels necessary even just voting for package
he wants to see.
George
On Tuesday 16 April 2002 15:08, you wrote:
> Yeah, pretty much. However, Freshports looks more developer centrix than
> end-user
> centric as Freshmeat appears to me.
>
> I think it is important to keep the end user who's going to be trying to
> make intelligent decisions about which ebuilds to download as your central
> audience.
>
> At 04:09 PM 3/16/2002 -0600, you wrote:
> > > The beauty of this? Those familiar with Freshmeat barely have to learn
> > > a new interface and the whole Freshmeat site has *got* to be open
> > > source available somewhere to make this a fast start towards this sort
> > > of vision.
> >
> >Do you essentially mean http://www.freshports.org/ with comments?
> >
> >_______________________________________________
> >gentoo-dev mailing list
> >gentoo-dev@gentoo.org
> >http://lists.gentoo.org/mailman/listinfo/gentoo-dev
>
> President
> www.cybrains.net
>
> "All things should be as simple as possible, but no simpler" -- Albert
> Einstein
>
> _______________________________________________
> gentoo-dev mailing list
> gentoo-dev@gentoo.org
> http://lists.gentoo.org/mailman/listinfo/gentoo-dev
next prev parent reply other threads:[~2002-03-17 1:04 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-16 19:46 [gentoo-dev] Unstable branch proposal - second round George Shapovalov
2002-03-16 20:59 ` George Shapovalov
2002-03-17 0:52 ` [gentoo-dev] multiple pkg state levels, was: Unstable branch proposal George Shapovalov
2002-04-16 21:29 ` [gentoo-dev] Unstable branch proposal - second round Michael Lang
2002-03-16 22:09 ` Brent Cook
2002-03-17 0:26 ` Daniel Mettler
2002-04-17 0:33 ` Michael Lang
2002-03-17 1:13 ` George Shapovalov
2002-03-17 19:53 ` [gentoo-dev] separate catalog for my ebuilds Giulio Eulisse
2002-03-17 21:40 ` Chad M. Huneycutt
2002-04-16 22:08 ` [gentoo-dev] Unstable branch proposal - second round Michael Lang
2002-03-17 1:04 ` George Shapovalov [this message]
2002-03-19 13:05 ` [gentoo-dev] Usb mouse issues with 2.4.17-r5 Michael M Nazaroff
2002-03-20 8:11 ` Stefan Jones
2002-03-25 11:23 ` [gentoo-dev] Re: Unstable branch proposal - second round Troy Dack
2002-03-25 14:57 ` Aaron Cohen
2002-03-28 3:22 ` Aaron Cohen
2002-03-28 6:52 ` George Shapovalov
2002-03-29 13:10 ` Chris Johnson
2002-03-30 11:04 ` George Shapovalov
2002-03-26 3:36 ` George Shapovalov
2002-03-29 23:40 ` Chris Johnson
2002-03-30 6:02 ` Troy Dack
2002-03-30 8:57 ` George Shapovalov
2002-03-30 9:03 ` Chris Johnson
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=200203170100.RAA29588@chamber.cco.caltech.edu \
--to=georges@its.caltech.edu \
--cc=gentoo-dev@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