On 31-08-2011 18:29:35 -0400, Aaron W. Swenson wrote:
You shouldn't let upstream jerk you or our users around, though. If I
want to build my packages with -march=native -mtune=native -pipe -O3
- -fzomg -freakin-fast -man -fo-sho, then by golly, let me.
We have a 'custom-cflags' USE flag. The
On Wednesday 31 August 2011 15:41:51 Corentin Chary wrote:
Hi,
some news about euscan (still available at http://euscan.iksaif.net)
- New design (yay !)
Glad you like it. Be sure to credit where you got it from, though.
--
Alex Legler a...@gentoo.org
Gentoo Security / Ruby
signature.asc
On Thu, Sep 1, 2011 at 9:23 AM, Alex Legler a...@gentoo.org wrote:
On Wednesday 31 August 2011 15:41:51 Corentin Chary wrote:
Hi,
some news about euscan (still available at http://euscan.iksaif.net)
- New design (yay !)
Glad you like it. Be sure to credit where you got it from, though.
Dne 1.9.2011 09:44, Corentin Chary napsal(a):
On Thu, Sep 1, 2011 at 9:23 AM, Alex Leglera...@gentoo.org wrote:
On Wednesday 31 August 2011 15:41:51 Corentin Chary wrote:
Hi,
some news about euscan (still available at http://euscan.iksaif.net)
- New design (yay !)
Glad you like it. Be
Btw I have feature request, could it remember the sorting method i set?
(so I don't have to click and reorder it every time i refresh)
Per-page or globally ?
--
Corentin Chary
http://xf.iksaif.net
Dne 1.9.2011 09:55, Corentin Chary napsal(a):
Btw I have feature request, could it remember the sorting method i set?
(so I don't have to click and reorder it every time i refresh)
Per-page or globally ?
I would say globaly i smore sane here
Tom
Addressed last bunch of suggestions :)
Tom
# Copyright 1999-2011 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/eclass/check-reqs.eclass,v 1.8 2011/08/22
04:46:31 vapier Exp $
# @ECLASS: check-reqs.eclass
# @MAINTAINER:
#
On Wed, 31 Aug 2011 15:41:51 +0200
Corentin Chary corentin.ch...@gmail.com wrote:
- Specific handlers for PyPi, RubyGems, pecl and PEAR packages (check
http://git.iksaif.net/?p=euscan.git;a=tree;f=pym/euscan/handlers;h=9a995dfcebe6beecce71851abb84a875cf6e5979;hb=HEAD
).
AFAICS that specific
On Thu, 1 Sep 2011 00:16:29 +0200
Ulrich Mueller u...@gentoo.org wrote:
On Wed, 31 Aug 2011, Mike Frysinger wrote:
installing the files unconditionally does fall into the
logrotate/xinetd category, so it should get punted. but people
should not end up with the depends installed all the
Hello,
A quick idea. Right now eclasses sometimes do API changes and start
yelling at users merging ebuilds using outdates APIs. This often means
users start filling bugs about outdated ebuilds requiring maintainers
either to ignore that or start updating old ebuilds retroactively.
Maybe we
On Thu, Sep 1, 2011 at 10:31 AM, Michał Górny mgo...@gentoo.org wrote:
On Wed, 31 Aug 2011 15:41:51 +0200
Corentin Chary corentin.ch...@gmail.com wrote:
- Specific handlers for PyPi, RubyGems, pecl and PEAR packages (check
On 1.9.2011 12.03, Michał Górny wrote:
Hello,
A quick idea. Right now eclasses sometimes do API changes and start
yelling at users merging ebuilds using outdates APIs. This often means
users start filling bugs about outdated ebuilds requiring maintainers
either to ignore that or start
On Thu, 01 Sep 2011 13:44:47 +0300
Petteri Räty betelge...@gentoo.org wrote:
On 1.9.2011 12.03, Michał Górny wrote:
Hello,
A quick idea. Right now eclasses sometimes do API changes and start
yelling at users merging ebuilds using outdates APIs. This often
means users start filling
On 1.9.2011 13.51, Michał Górny wrote:
On Thu, 01 Sep 2011 13:44:47 +0300
Petteri Räty betelge...@gentoo.org wrote:
On 1.9.2011 12.03, Michał Górny wrote:
Hello,
A quick idea. Right now eclasses sometimes do API changes and start
yelling at users merging ebuilds using outdates APIs. This
On Thu, 01 Sep 2011 14:02:11 +0300
Petteri Räty betelge...@gentoo.org wrote:
On 1.9.2011 13.51, Michał Górny wrote:
On Thu, 01 Sep 2011 13:44:47 +0300
Petteri Räty betelge...@gentoo.org wrote:
On 1.9.2011 12.03, Michał Górny wrote:
Hello,
A quick idea. Right now eclasses sometimes
On 1.9.2011 14.31, Michał Górny wrote:
On Thu, 01 Sep 2011 14:02:11 +0300
Petteri Räty betelge...@gentoo.org wrote:
On 1.9.2011 13.51, Michał Górny wrote:
On Thu, 01 Sep 2011 13:44:47 +0300
Petteri Räty betelge...@gentoo.org wrote:
On 1.9.2011 12.03, Michał Górny wrote:
Hello,
A quick
2011/9/1 Tomáš Chvátal scarab...@gentoo.org:
Dne 1.9.2011 09:55, Corentin Chary napsal(a):
Btw I have feature request, could it remember the sorting method i set?
(so I don't have to click and reorder it every time i refresh)
Per-page or globally ?
I would say globaly i smore sane here
I
Hello,
Our bash-completion.eclass is awful and ugly. I'm not even talking
about flags and stuff now but dobashcompletion() itself.
That function doesn't follow do*() argument scheme; it matches rather
one used by new*() funcs. Sadly, a number of ebuilds is using that
scheme to rename installed
Dne 1.9.2011 14:48, Michał Górny napsal(a):
Hello,
Our bash-completion.eclass is awful and ugly. I'm not even talking
about flags and stuff now but dobashcompletion() itself.
That function doesn't follow do*() argument scheme; it matches rather
one used by new*() funcs. Sadly, a number of
On 09/01/2011 07:48 AM, Michał Górny wrote:
Hello,
Our bash-completion.eclass is awful and ugly. I'm not even talking
about flags and stuff now but dobashcompletion() itself.
That function doesn't follow do*() argument scheme; it matches rather
one used by new*() funcs. Sadly, a number of
On Thu, 01 Sep 2011 14:56:42 +0200
Tomáš Chvátal scarab...@gentoo.org wrote:
That function doesn't follow do*() argument scheme; it matches
rather one used by new*() funcs. Sadly, a number of ebuilds is
using that scheme to rename installed file.
Furthermore, it uses two eclass
Dne 1.9.2011 15:15, Michał Górny napsal(a):
On Thu, 01 Sep 2011 14:56:42 +0200
Tomáš Chvátalscarab...@gentoo.org wrote:
That function doesn't follow do*() argument scheme; it matches
rather one used by new*() funcs. Sadly, a number of ebuilds is
using that scheme to rename installed file.
# Jesus Rivero neurog...@gentoo.org (01 Sep 2011)
# Masked for removal in 30 days. This package does not
# work with any version of app-accessibility/speakup
# anymore.
app-accessibility/speakup-utils
--
Jesus Rivero (Neurogeek)
Gentoo Developer
On Thu, 1 Sep 2011, Michał Górny wrote:
I think the way to go would be to reimplement it completely. Maybe
just put dobashcomp() and newbashcomp() functions in eutils (to not
collide) and deprecate bash-completion.eclass?
I'd rather keep this in a separate bash-completion-2.eclass.
We
On Thu, 1 Sep 2011 15:27:12 +0200
Ulrich Mueller u...@gentoo.org wrote:
On Thu, 1 Sep 2011, Michał Górny wrote:
I think the way to go would be to reimplement it completely. Maybe
just put dobashcomp() and newbashcomp() functions in eutils (to not
collide) and deprecate
On 14:44 Thu 01 Sep , Petteri Räty wrote:
One thing to note is that we should get eqawarn into the next EAPI.
Why?
--
Thanks,
Donnie
Donnie Berkholz
Council Member / Sr. Developer
Gentoo Linux
Blog: http://dberkholz.com
pgpC80OrHx438.pgp
Description: PGP signature
On 15:20 Thu 01 Sep , Tomáš Chvátal wrote:
Dne 1.9.2011 15:15, Michał Górny napsal(a):
We can either go with a new func and retroactively replace the
eclass, or retroactively fix all uses and fix the old funcs.
As even if you fix main tree you can't ensure that you won't mess with
On Wed, Aug 31, 2011 at 3:41 PM, Corentin Chary
corentin.ch...@gmail.com wrote:
Hi,
some news about euscan (still available at http://euscan.iksaif.net)
- New design (yay !)
- Atom feeds available for each herd/category/maintainer/package
(http://euscan.iksaif.net/maintainers/59/feed/)
-
On Thu, 1 Sep 2011, Michał Górny wrote:
So, here it goes. However, I'm not sure if that even deserves
a dedicated function as the destination is pretty constant.
# @BLURB: A few quick functions to install bash-completion files
# @DESCRIPTION:
# A few simple functions to help installing
On 09/01/2011 04:02 AM, Petteri Räty wrote:
Have Portage defaults so that users only see if them if they read the
merge logs and then developer profiles can set the settings to log them?
As far as I know, this is already the case. The current default set by
portage in
On 1.9.2011 17.12, Donnie Berkholz wrote:
On 14:44 Thu 01 Sep , Petteri Räty wrote:
One thing to note is that we should get eqawarn into the next EAPI.
Why?
So that it wouldn't fall back on einfo where not available.
Regards,
Petteri
On Thu, 01 Sep 2011 08:25:14 -0700
Zac Medico zmed...@gentoo.org wrote:
On 09/01/2011 04:02 AM, Petteri Räty wrote:
Have Portage defaults so that users only see if them if they read
the merge logs and then developer profiles can set the settings to
log them?
As far as I know, this is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/01/2011 09:19 AM, Michał Górny wrote:
On Thu, 01 Sep 2011 08:25:14 -0700 Zac Medico zmed...@gentoo.org
wrote:
On 09/01/2011 04:02 AM, Petteri Räty wrote:
Have Portage defaults so that users only see if them if they
read the merge logs and
This patch series adds thin manifest support. While mini-manifest feature
exists in funtoo, that functionality is a global toggle- either all are mini,
or none.
This series makes thin controllable per repository via layout.conf; if
the file exists and has 'thin-manifest = true' in it, the
'thin' is just distfiles. This is primarily useful when the ebuild
lives in a vcs- git for example, which already has it's own checksums
to rely on.
---
pym/portage/manifest.py | 149 ++--
pym/portage/package/ebuild/digestcheck.py |2 +-
2 files
This enables controling the behaviour (creation and validation) per
repo, and while mildly ugly, refactors in the right direction.
---
bin/ebuild|5 +++--
bin/repoman |8 ++--
pym/_emerge/EbuildFetcher.py |
36 matches
Mail list logo
