Branko Badrljica wrote:
Since I might not be the only tinkerer on Gentoo to try stuff like that
and since it took me a day to find this, maybe it wouldn't hurt to check
for this kind of thing in portage ?
At the very least failed cp should stop emerge...
Well there isn't a single place
Jonas Bernoulli wrote:
Hi
May I suggest that you add links so that anoncvs.g.o and sources.g.o
link to one another. Users might find one of those pages and think
that's all there is to it. However both of the pages contain
information not available on the other. anoncvs.g.o mentions git and
Doug Goldstein wrote:
Petteri Räty wrote:
Branko Badrljica wrote:
Since I might not be the only tinkerer on Gentoo to try stuff like that
and since it took me a day to find this, maybe it wouldn't hurt to check
for this kind of thing in portage ?
At the very least failed cp should stop
Tobias Scherbaum wrote:
Thilo Bangert wrote:
Now what do people think about extending metadata.xml so that you
could have these
bugs filed automatically when there are no open bugs? Something like
a auto-stable-request enabled=true/
element with the DTD setting the default as true and you
Thilo Bangert wrote:
Donnie Berkholz dberkh...@gentoo.org said:
On 05:10 Sun 14 Dec , Petteri Räty wrote:
I added support for filing stable requests directly from my stable
candidate RSS feed.
For those that don't read planet Gentoo the feed can be found here:
http
Tiziano Müller wrote:
Am Sonntag, den 14.12.2008, 18:33 +0300 schrieb Peter Volkov:
В Вск, 14/12/2008 в 05:10 +0200, Petteri Räty пишет:
Now what do people think about extending metadata.xml so that you could
have these bugs filed automatically when there are no open bugs?
Is it possible
I added support for filing stable requests directly from my stable
candidate RSS feed.
For those that don't read planet Gentoo the feed can be found here:
http://gentoo.petteriraty.eu/stable.rss
Now what do people think about extending metadata.xml so that you could
have these
bugs filed
Robert R. Russell wrote:
My personal opinion on this matter is pick one of the following:
1) perform the bugfix without a version bump and remain at the current EAPI
version
2) perform the bugfix with a version bump and remain at the current EAPI
version
3) perform the bugfix with a
Federico Ferri wrote:
Hello,
today I hit this annoyance, because my laptop hung in the middle of an
'emerge -e @world' (checking that my world set compiles with
gcc-4.3... stopped at ~ 300 of 700 :S )
Consider using emerge --keep-going next time.
I was looking for an entry in
Maciej Mrozowski wrote:
Following advise from https://bugs.gentoo.org/show_bug.cgi?id=250179, I'm
bringing it here.
I think this is probably a good idea after EAPI 2 is stable and we
eliminate built_with_use usage from the tree. I think having stuff build
out of the box instead of dying in
Ciaran McCreesh wrote:
On Thu, 27 Nov 2008 19:43:59 +
Ciaran McCreesh [EMAIL PROTECTED] wrote:
The DEFINED_PHASES variable will contain a space separated arbitrarily
ordered list of phase names. A phase name is listed in DEFINED_PHASES
if and only if the ebuild or an eclass used by that
Jan Kundrát wrote:
kashani wrote:
How easy is it to checkout current GDP docs
Append ?passthru=1 to the end of the URL.
and make changes to them?
I take it you want to make a patch. In such case, edit the file and
submit the diff via Bugzilla.
Cheers,
-jkt
Or use anoncvs for
Michael Hammer wrote:
* Mark Loeser [EMAIL PROTECTED] [081112 00:46]:
What are others feelings on this?
I like the idea!
What issues do you see with having a wiki?
Pages of poor quality with wrong informations.
Do you see anyway to resolve the issue you see with us having a
Zac Medico wrote:
Christoph Mende wrote:
Hi,
I'm currently working on a new eclass for Xfce4 that, as opposed to the
previous ones (xfce42.eclass, xfce44.eclass), is supposed to be used
for all versions. Now the most logical name for an eclass like that
would be xfce4.eclass, except that
Doug Goldstein wrote:
Doug Goldstein wrote:
Doug Goldstein wrote:
While the rule of thumb has been if an eclass needs something it should
provide it's own depends. However the virtualx eclass needs to be
different simply because in some cases it's only uses for tests (this is
it's most
Marius Mauch kirjoitti:
On Tue, 14 Oct 2008 10:59:39 +0200
Jose Luis Rivero [EMAIL PROTECTED] wrote:
On Mon, Oct 13, 2008 at 05:38:34PM -0700, Donnie Berkholz wrote:
On 02:03 Tue 14 Oct , Jose Luis Rivero wrote:
There are some others sceneries but are not so common as the one
presented
Matti Bickel kirjoitti:
Hi folks,
While fixing bug #240060 I touched fox.eclass.
In the process, I updated the eclass to
* use versionator
* cut support for fox-1.0 (loong outdated)
* cut support for fox-1.5
* use eautomake instead of =automake-1.4*
* use emake
Doug Goldstein kirjoitti:
As some people may have already noticed, I have recently added OpenRC
0.3.0 to the tree. This will be the stabilization candidate in
approximately 30 days.
I encourage everyone to kick the tires on this one.
Current Bugs: *http://tinyurl.com/4housz*
That list
Currently the doc use flag on gtk-doc using packages does not control
doc installation but instead whether to rebuild them so that they are
properly cross linked. I think we should be using a separate use flag
from doc for this purpose. Any comments?
15:40 @Betelgeuse EvaSDK: Just change the doc
Mart Raudsepp kirjoitti:
On P, 2008-10-05 at 20:34 +0200, Thomas Sachau wrote:
Rémi Cardona schrieb:
Thomas Sachau a écrit :
Why not do both (rebuild and install) with the doc useflag and none of
both, if it is not set? Imho
the doc flag is for control of installation for (additional) docs,
Just a reminder to everyone that when you migrate to EAPI 2 in order to
use use dependencies remember to migrate your src_compile function too
or you will be running econf twice if you have a custom src_compile
function. econf will first be run by the default src_configure function
and then by
Nirbheek Chauhan kirjoitti:
On Sat, Sep 27, 2008 at 3:47 PM, Thomas Sachau [EMAIL PROTECTED] wrote:
So what about this one?
default_src_install() {
if [ -f Makefile ] || [ -f GNUmakefile ] || [ -f makefile ]; then
emake DESTDIR=${D} install || die emake install failed
Ciaran McCreesh kirjoitti:
On Mon, 29 Sep 2008 21:39:41 +1300
Alistair Bush [EMAIL PROTECTED] wrote:
Anyway, would be nice to get some feedback, idea's on this and
hopefully also a more detailed explaination from a pm's perspective
(if there is one).
For current EAPIs, there's nothing
+# Petteri Räty [EMAIL PROTECTED] (29 Sep 2008)
+# Live ebuilds are more appropriate to overlays.
+# See https://bugs.gentoo.org/show_bug.cgi?id=227629
+# for more details.
+dev-lisp/abcl-cvs
+
signature.asc
Description: OpenPGP digital signature
Alexis Ballier kirjoitti:
On Mon, 29 Sep 2008 09:38:41 +0200
Alexis Ballier [EMAIL PROTECTED] wrote:
Hi Diego,
EAPI=2
[...]
src_compile() {
WX_GTK_VER=2.8
need-wxwidgets unicode
econf \
This causes me a configure failure because I don't have a system
wxwdigets
Robin H. Johnson kirjoitti:
On Sat, Sep 27, 2008 at 12:48:41AM +, Saleem Abdulrasool (compnerd) wrote:
compnerd08/09/27 00:48:41
Added:cairo-1.8.0.ebuild
Log:
version bump
(Portage version: 2.2_rc9/cvs/Linux 2.6.27-rc3-git3 i686)
Revision ChangesPath
1.1
Bo Ørsted Andresen kirjoitti:
On Monday 22 September 2008 22:25:20 Petteri Räty wrote:
If you mean something like
built_with_use cat/foo coolfeature || ewarn bar will be more useful if you rebuild cat/foo with USE=coolfeature
then you can use
has_version 'cat/foo[coolfeature
Alexis Ballier kirjoitti:
On Tue, 23 Sep 2008 23:33:44 +0300
Petteri Räty [EMAIL PROTECTED] wrote:
Bo Ørsted Andresen kirjoitti:
On Monday 22 September 2008 22:25:20 Petteri Räty wrote:
If you mean something like
built_with_use cat/foo coolfeature || ewarn bar will be more
useful if you
David Leverton kirjoitti:
On Saturday 20 September 2008 18:15:27 Alexis Ballier wrote:
I can think of checks like:
- foo is a dep/rdep of bar
- foo has a plugin like architecture
- bar will work with minimal foo
- most people will expect some features in bar that come with foo's
plugins
- we
When EAPI 2 goes live built_with_use should probably die for most cases.
Are there valid use cases for built_with_use that are not covered by the
use deps in EAPI 2? If there are we could add a switch like --noeapi2die
to it.
Regards,
Petteri
signature.asc
Description: OpenPGP digital
Alexis Ballier kirjoitti:
Hi,
When EAPI 2 goes live built_with_use should probably die for most
cases.
I don't understand here: you mean die like being removed or die like
the die call in an ebuild? If I understood correctly the following it
should be the latter.
Well we could go with
Thomas Sachau kirjoitti:
I see, we have a default src_unpack and a default src_compile but a default
src_install is still
missing. Here is my suggestion (taken and modified from bug 33544):
src_install() {
if [ -f Makefile -o -f GNUmakefile -o -f makefile ]; then
emake
Ciaran McCreesh kirjoitti:
On Sun, 14 Sep 2008 15:28:09 -0700
Donnie Berkholz [EMAIL PROTECTED] wrote:
On 21:55 Sun 14 Sep , Ciaran McCreesh wrote:
On Sun, 14 Sep 2008 23:51:11 +0300
Petteri Räty [EMAIL PROTECTED] wrote:
Hopefully someone formats it to a real GLEP before that.
git clone
David Leverton kirjoitti:
On Thursday 11 September 2008 21:06:48 Doug Goldstein wrote:
Tobias Scherbaum wrote:
Luca Barbato wrote:
I don't see any problems with it.
+1
Tobias
+1
Since this latest version hasn't generated any noticeable disagreement, could
the Council please formally
Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file name we could
have icedtea-1.2:1.6.ebuildN and icedtea-1.2:1.7.ebuildN. This
particular situation
Donnie Berkholz kirjoitti:
On 14:56 Fri 12 Sep , Doug Goldstein wrote:
Petteri Räty wrote:
Icedtea has two release tracks. One for the 1.7 OpenJDK code base and
one for the 1.6 code base. They have independent version numbering so
they can have collisions. By moving the slot to the file
Donnie Berkholz kirjoitti:
On 22:21 Fri 12 Sep , Petteri Räty wrote:
I do know how to get around it, I did state that in my original email.
As it happens we are having a discussion on gentoo-java mailing list on
whether we should use icedtea-openjdk build.icedtea version.ebuild
or have
Ciaran McCreesh kirjoitti:
On Tue, 09 Sep 2008 16:31:08 +0300
Petteri Räty [EMAIL PROTECTED] wrote:
Jorge Manuel B. S. Vicetto kirjoitti:
and cardoe's earlier request to the council ml, can the council
members discuss this proposal and consider voting it?
Does anyone have any objections
Jorge Manuel B. S. Vicetto kirjoitti:
and cardoe's earlier request to the council ml, can the council members
discuss this proposal and consider voting it?
Does anyone have any objections to this proposal?
I won't approve it for use in the tree before it's written as a GLEP in
order to
Alec Warner kirjoitti:
On Fri, Sep 5, 2008 at 12:39 AM, Zac Medico [EMAIL PROTECTED] wrote:
David Leverton wrote:
2008/9/5 Zac Medico [EMAIL PROTECTED]:
Both approaches are essentially equivalent but it's a little simpler
for ebuild writer if they don't have to customize the output file name.
Peter Alfredsen kirjoitti:
Hi,
It won't be long before I ask for poppler-0.8 and -bindings to be
stabilized. This will bump the soname for poppler and force a rebuild
of all packages depending on it. I've opened a tracker bug at
http://bugs.gentoo.org/235897 where you can add a comment or
. Unless objections come out the new news item will be
committed at the same time as rc8 (rc8 will have an update man portage
page describing world_sets).
Title: World file handling changes in Portage-2.2
Author: Petteri Räty [EMAIL PROTECTED]
Author: Zac Medico [EMAIL PROTECTED]
Content-Type: text
Zac Medico kirjoitti:
* Default phase function implementations for older EAPIs are
accessible via functions having names that start with 'eapi',
followed by the EAPI value.
What's the benefit of this feature?
Regards,
Petteri
signature.asc
Description: OpenPGP digital signature
Steve Dibb kirjoitti:
Are there ever any cases where we could just simply put the use flag as
restricted in the global package.use.mask and then unrestrict them in
the profiles ones if, for example, it only worked on one or a few
arches? Or is the best policy always to mask it on each
Friedrich Oslage kirjoitti:
Maybe we should ask Recruiters what most people answered to that
eom-quiz question :)
I have been instructing people to adjust the files themselves. The
changes affect only the package in question and as such it falls under
the responsibility of the maintainer of
Zac Medico kirjoitti:
Petteri Räty wrote:
Zac Medico kirjoitti:
* Default phase function implementations for older EAPIs are
accessible via functions having names that start with 'eapi',
followed by the EAPI value.
What's the benefit of this feature?
In some cases it might
Thomas Anderson kirjoitti:
Hi,
Currently we have default_* functions implemented in
portage(paludis has these too)
which allow the default implementation of a particular phase
to be called. Another handy function in the default_* series is
function
Robin H. Johnson kirjoitti:
Hi folks,
Sorry that it's taken this long to get completed, but the Jeeves
replacement, Willikins, is finally 99% done, and ready to join lots of
channels.
Getting the bot out there
-
If you would like to have the new bot in your #gentoo-*
Jim Ramsay kirjoitti:
I've run into it a few times now that fluxbox users running Gentoo
wonder why they can't get icons to work in the fluxbox menus. The
short answer is that 'imlib' is off by default in many profiles,
including default-linux/amd64/2007.0/desktop and
Marius Mauch kirjoitti:
If someone wants to use it I can add it on the tree (after the normal
review process and being better tested), but I'll only be doing it
when there is an actual demand for it (no point in adding an eclass that
nobody uses).
I have been long thinking about adding
Ciaran McCreesh kirjoitti:
On Sun, 13 Jul 2008 16:16:23 -0700
Alec Warner [EMAIL PROTECTED] wrote:
As far as could be determined by the members at the meeting there no
compelling examples in Gentoo who to change or add global scope
functions in future EAPIs. As such those problems as stated
Marius Mauch kirjoitti:
So, is this something ebuild maintainers would like in general, or does
such a feature cause you nightmares?
I have actually been thinking about writing support for this into the
Java eclasses because most Java upstreams use .zip files and we need
app-arch/unzip in
Ciaran McCreesh kirjoitti:
On Tue, 15 Jul 2008 18:58:01 +0300
Petteri Räty [EMAIL PROTECTED] wrote:
Yes I can think a lot of features like this that would be of great
use in the main tree but as long as Portage is the only official and
stable package manager and doesn't support the things you
Łukasz Damentko kirjoitti:
Dear Gentoo Community,
Here are your verified and long-awaited results.
Gentoo Council for term 2008/2009 will be:
Donnie Berkholz (dberkholz)
Mark Loeser (Halcy0n)
Diego Petteno (Flameeyes)
Petteri Raty (Betelgeuse)
Luca Barbato (lu_zero)
Markus Ullmann (Jokey)
Jeroen Roovers kirjoitti:
-
1) How do you feel when you receive an early version bump request?
I don't mind as I don't have the time to follow upstreams that closely
for the hundreds of Java packages out there.
2) If you had your way, would you discourage users from filing early
Albert Zeyer kirjoitti:
On Sat, 2008-06-21 at 09:35 +0200, Tiziano Müller wrote:
Donnie Berkholz wrote:
On 14:52 Thu 05 Jun , Samuli Suominen wrote:
# Samuli Suominen [EMAIL PROTECTED] (05 Jun 2008)
# Masked for removal in ~30 days by treecleaners.
# Replaced by USE libffi in
Mike Frysinger kirjoitti:
On Saturday 28 June 2008, Petteri Räty wrote:
Arfrever Frehtes Taifersar Arahesis kirjoitti:
I would like to suggest that default LDFLAGS in Gentoo contain the
following flags: -Wl,-O1,--hash-style=gnu,--sort-common.
-O1 enables some basic optimizations.
At least
Arfrever Frehtes Taifersar Arahesis kirjoitti:
I would like to suggest that default LDFLAGS in Gentoo contain the following
flags: -Wl,-O1,--hash-style=gnu,--sort-common.
-O1 enables some basic optimizations.
At least adding -O1 should not be problematic. I think vapier was
already
Doug Goldstein kirjoitti:
All,
Here's a GLEP for the addition of USE flag descriptions to package
metadata. It does not address any future ideas that others may have had
or suggested. It merely gives developers the necessary tools to
document their USE flag usage it better detail on a per
Josh Saddler kirjoitti:
Łukasz Damentko wrote:
Hi guys,
Nominations for the Gentoo Council 2008/2009 are open now and will be
open for the next two weeks (until 23:59 UTC, 18/06/2008).
Now that nominations are officially open, I nominate the current council
members (again):
amne
Mike Pagano kirjoitti:
Mike Pagano [EMAIL PROTECTED] (19 May 2008)
Masked for removal in 30 days. Upstream has changed
name to crossvc, which is available in the tree.
(bug #213496)
---
Mike Pagano
Gentoo Developer - Kernel Project
E-Mail : [EMAIL PROTECTED]
GnuPG
Wulf C. Krueger kirjoitti:
How to gain power the easy way and obsolete conflict resolution in just
one commit:
http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/proj/en/devrel/policy.xml?r1=1.18r2=1.19
Please use the appropriate mailing list. Nothing technical here. This
thread
Santiago M. Mola kirjoitti:
Thoughts? Isn't there anyone else willing to keep Nazi symbols outside
forums? If yes, at the expense of punting all politics or just as a
special case?
Again this is the wrong mailing list. I don't see this thread having any
technical content.
Regards,
Petteri
Luca Barbato kirjoitti:
Alistair Bush wrote:
++. I actually have no problem with agreeing with it, currently my
problem is the complete and utter lack of any _planned_ upgrade path.
What do we think users are going to be saying at the end of the year
when after every sync they have to
Diego 'Flameeyes' Pettenò kirjoitti:
Probably the best thing would be to get a better tool than
revdep-rebuild to handle broken .la files, as revdep-rebuild forces a
timewasting rebuild, while a good fix could be just a sed -i -e
's:/usr/lib\(64\)\?/lib\(.*\).la:-l\2:' on all the .la files,
Mateusz A. Mierzwin'ski kirjoitti:
Richard Freeman pisze:
Mateusz A. Mierzwin'ski wrote:
And I strongly suggest to leave old mechanism of portage, because we
saw couple times what _GREAT_ automatic makes with distro - eg.
Mandriva with all creators and cheap installer - couple apps not
Marijn Schouten (hkBst) kirjoitti:
Hi list,
it seems I have been using some fragile sed expression and I'd like to
tap the collective
wisdom for avoiding doing that in the future.
dev-scheme/slib-3.1.5-r1 currently does
sed s_prefix = /usr/local/_prefix = ${D}/usr/_ -i Makefile
to make it
Vlastimil Babka kirjoitti:
*portage-2.1.5_rc1 (04 Apr 2008)
04 Apr 2008; Zac Medico [EMAIL PROTECTED] +portage-2.1.5_rc1.ebuild:
2.1.5_rc1 release. In the event that a previously installed package has
since been masked, emerge will no longer perform an automatic downgrade
as part of a
Petteri Räty kirjoitti:
I checked the current slacker script and it checks for having at least
one commit in last 60 days. We could of course just change the slacker
script to list the activity for everyone during the last 60 days and
leave the interpretation to undertakers.
Regards
Mike Pagano kirjoitti:
On Monday 07 April 2008 04:37:18 pm Petteri Räty wrote:
Petteri Räty kirjoitti:
So I wrote a new slacker script that gets the active developers from
LDAP and checks the activity for the last 60 days. One repoman commit
should equal a couple entries on history
Jorge Manuel B. S. Vicetto kirjoitti:
Petteri Räty wrote:
I agree with the above point.
Also, as I recall, both Pettery (betelgeuse) and Denis (calchan) have
stated before that we no longer have any queue of people waiting on
recruiters to join Gentoo. I'm not seeing an avalanche of new blood
Fabian Groffen kirjoitti:
On 02-04-2008 21:21:25 -0400, Richard Freeman wrote:
Would it make more sense to just make a policy that failure to maintain
packages that you're maintainer on will result in getting removed as the
maintainer, with said packages going up for grabs? Devs who keep
Ciaran McCreesh kirjoitti:
On Thu, 03 Apr 2008 11:35:20 +
Jorge Manuel B. S. Vicetto [EMAIL PROTECTED] wrote:
True, but with some acls we could also have a different model where
people worked on parts of the tree and where commit privileges didn't
pose so many security risks. With the
Chrissy Fullam kirjoitti:
Petteri Räty wrote:
Mike Frysinger kirjoitti:
This is your monthly friendly reminder ! Same bat time (typically the
2nd Thursday at 2000 UTC / 1600 EST), same bat channel
(#gentoo-council @ irc.freenode.net) !
If you have something you'd wish for us to chat about
Mike Frysinger kirjoitti:
This is your monthly friendly reminder ! Same bat time (typically
the 2nd Thursday at 2000 UTC / 1600 EST), same bat channel
(#gentoo-council @ irc.freenode.net) !
If you have something you'd wish for us to chat about, maybe even
vote on, let us know ! Simply reply
Mike Auty kirjoitti:
Petteri Räty wrote:
Defining required amount of activity for ebuild devs. I would like us
to raise the required amount of activity for ebuild devs.
Given that the low number of developers is ranked as our number one
problem in Donnie's informal survey[1], taking any kind
Wulf C. Krueger kirjoitti:
On Wednesday, 02. April 2008 22:46:16 Petteri Räty wrote:
How does having the average time between commits be at most a week
sound and if it goes under that, undertakers will get a notification?
It sounds like you're trying to get rid of someone.
I don't have
Mike Auty kirjoitti:
Petteri Räty wrote:
If you can't manage weekly commits, you can't respond to security
issues either.
I can see your point, I was more thinking about developers who have
maybe one or two small packages that don't have many version bumps or
bugs. They may be entirely
Ciaran McCreesh kirjoitti:
On Sun, 30 Mar 2008 17:18:44 -0400
Mark Loeser [EMAIL PROTECTED] wrote:
If it is something we want to move forward with, it should be
introduced at the package manager level instead of being an in-tree
package manager specific feature.
cat
Steve Long kirjoitti:
I don't see how it would wreak more havoc than a novice using, eg ANT from
Java which s/he is comfortable with, and then further having to learn BASH
peculiarities when things don't fit with the eclass. But yeah, the fun is
what attracts me to the idea more than anything.
Rémi Cardona kirjoitti:
Petteri Räty a écrit :
http://archives.gentoo.org/gentoo-dev/msg_a57bf5f459324975bae8843fe7cdf469.xml
Sorry I didn't respond to you Petteri, but this is clearly missing
packages. For sure, it's missing gnome-games which inherits both the
gnome2 and the games
Rémi Cardona kirjoitti:
Now, basically, if the portage metadata or QA people could tell me a way
to figure *all* the ebuilds that inherit gnome2 *and* have a
pkg_preinst() function somewhere (either in the ebuild or in an eclass
somewhere) I'd really appreciate it, as I really don't want to
Christian Faulhammer kirjoitti:
Hi,
in the Emacs overlay we imported the bzr.eclass from the xeffects
overlay. In the near future Emacs development will switch from CVS to
Bazaar and thus we need the new eclass in Portage to still provide our
live ebuilds from app-editors/emacs-cvs. Question
David Leverton kirjoitti:
On Friday 14 March 2008 07:14:23 Rémi Cardona wrote:
- the gnome2 eclass now has a pkg_preinst, if you do multiple
inherits, make sure that gnome2_pkg_preinst is called too. The
_games_eclass_ is one of those.
Maybe worth adding a dummy to the current version of
Rémi Cardona kirjoitti:
This is where I kindly request the help of fellow Gentoo devs and PM
developers :
- the gnome2 eclass now has a pkg_preinst, if you do multiple inherits,
make sure that gnome2_pkg_preinst is called too. The _games_eclass_ is
one of those.
I only found two ebuilds
David Leverton kirjoitti:
On Friday 14 March 2008 12:14:39 Petteri Räty wrote:
David Leverton kirjoitti:
Maybe worth adding a dummy to the current version of the eclass so that
ebuilds can be updated now, instead of suddenly all at once as soon as
the new eclass is committed?
And break
Natanael Copa kirjoitti:
On Thu, 2008-03-13 at 00:35 +0100, Fabio Erculiani wrote:
I offer my help to fix DEPEND/RDEPEND split issues which is causing me
a lot of headaches (along with localizations).
For reference, please have a look here: http://planet.sabayonlinux.org/?p=105
I'm another
Fabio Erculiani kirjoitti:
[02:31] Halcy0n lxnay: we offer all of our work that you base your
distribution off, and you don't contribute back at all, in any way.
^^ This is a really stupid sentence. It seems some of you don't even
realize how many users we brought to Gentoo, and this is really
[EMAIL PROTECTED] kirjoitti:
Well I'm a newcomer to Gentoo and never heard of Sabayon (great project
btw). Knowing no one here or there, nor any history:
Never heard of and you say it's a great project?
This conversation reminds me of Human Resources. They always have
'procedures' and
solar reported that he had ebuild submissions blindly using EAPI=1 so we
hopefully made the text better reflect that it should not be used unless
absolutely needed.
Regards,
Petteri
[EMAIL PROTECTED] /usr/portage $ cvs diff -r 1.44 skel.ebuild
Index: skel.ebuild
One of those people working on those weird paper weights. This time our
monkey comes from the world of alphas. Tobias hails from Germany (there
seems to be no end). He works as a sysadmin so perhaps he will some idea
about stability. He is the author of pymetar and carl (emerge and try).
Petteri Räty kirjoitti:
One of those people working on those weird paper weights. This time our
monkey comes from the world of alphas. Tobias hails from Germany (there
seems to be no end). He works as a sysadmin so perhaps he will some idea
about stability. He is the author of pymetar and carl
Joining us from the zoos of Florida, we have Kenneth keninsert random
numbers here Prugh. Ken did such a fine job testing all those random
packages for amd64 that it will be the sole purpose of his life from now
on. He tells me his hobby is to learn new programming languages so I
guess he
Ulrich Mueller kirjoitti:
Isn't what you wrote the existing policy?
If it is, then the last question of the end-quiz should be changed:
| 19. You are bumping foomatic's ebuild from version 1.5 to version
| 2.0. This new version is a massive rewrite which introduces
| huge changes to
Jeroen Roovers kirjoitti:
On 01 Mar 2008 05:30:01
Mike Frysinger [EMAIL PROTECTED] wrote:
This is your monthly friendly reminder ! Same bat time (typically
the 2nd Thursday at 2000 UTC / 1600 EST), same bat channel
(#gentoo-council @ irc.freenode.net) !
If you have something you'd wish for
Hailing from the Venezuela, more precisely Caracas, we have Ricardo
ricmm Mendoza. When he's not fighting in the jungles, he likes to play
around with those expensive paper weights that some people call mips
computers. Luckily for him he will be soon moving to the comfort of
Europe. Now it's
Markus Ullmann kirjoitti:
So giving both (devs and users) an automated way of working with that
would help a lot IMHO.
like the user submits using
echangelog My cool change
repoman submit
then the dev gets a diff or whatever against current state and then just
does
repoman accept or
Thomas Anderson kirjoitti:
Please elaborate on how a full.fledged developer would differ from a
package maintainer technically. What requirements and/or
priviledges do you think could be reduced?
Marius
Perhaps there could be some honor code system at least, where the package
maintainer
Thomas Anderson kirjoitti:
Arch Testers don't have tree access. This proposal gives the package
maintainer the ability to commit their changes.
How would you ensure ebuild quality for these package maintainers?
Regards,
Petteri
signature.asc
Description: OpenPGP digital signature
Thomas Anderson kirjoitti:
On Wednesday 05 March 2008 16:05:09 Petteri Räty wrote:
Thomas Anderson kirjoitti:
Arch Testers don't have tree access. This proposal gives the package
maintainer the ability to commit their changes.
How would you ensure ebuild quality for these package maintainers
401 - 500 of 893 matches
Mail list logo
