On Mon, 14 May 2012 07:23:35 +0200
Hans de Graaff gra...@gentoo.org wrote:
On Sun, 2012-05-13 at 16:27 -0400, Mike Gilbert wrote:
To make ebuilds utilizing python-distutils-ng.eclass usable
out-of-the-box, the python team would like to add the following to
make.defaults in the base
After some Google-searching, I think I've figured out how to implement
automounting under mdev. I'd like to put in as much sanity-checking
into the script as possible. Right now I have 1 USB stick plugged in as
/dev/sdb. Th hard drive is /dev/sda. The removable data is readable
like so...
On Mon, May 14, 2012 at 03:53:53AM -0400, Walter Dnes wrote:
After some Google-searching, I think I've figured out how to implement
automounting under mdev. I'd like to put in as much sanity-checking
into the script as possible. Right now I have 1 USB stick plugged in as
/dev/sdb. Th hard
2012-05-14 06:58:30 Duncan napisał(a):
Ulrich Mueller posted on Sat, 12 May 2012 20:39:05 +0200 as excerpted:
On Sat, 12 May 2012, Michał Górny wrote:
EXTRA_EMAKE isn't supposed to be mentioned there. It's an internal use
variable for users who need to pass something specific to make.
On 5/14/2012 12:50 AM, Ben de Groot wrote:
On 14 May 2012 04:27, Mike Gilbert flop...@gentoo.org wrote:
To make ebuilds utilizing python-distutils-ng.eclass usable
out-of-the-box, the python team would like to add the following to
make.defaults in the base profile.
PYTHON_TARGETS=python2_7
El lun, 14-05-2012 a las 11:09 -0400, Mike Gilbert escribió:
On 5/14/2012 12:50 AM, Ben de Groot wrote:
On 14 May 2012 04:27, Mike Gilbert flop...@gentoo.org wrote:
To make ebuilds utilizing python-distutils-ng.eclass usable
out-of-the-box, the python team would like to add the following to
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
documentation then?
hasufell schrieb:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
documentation then?
-Werror is basically saying that it is
On Monday 14 May 2012 03:53:53 Walter Dnes wrote:
My question... is this API stable or deprecated? I.e. can I count on
it being around for a while? I figure this question is a developer type
question rather than ordinary user type.
if userspace is relying on stuff in /sys, then it's part
On Monday 14 May 2012 11:44:17 hasufell wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
documentation then?
the common
On Mon, 2012-05-14 at 17:44 +0200, hasufell wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
documentation then?
WD cat /sys/block/sda/removable
WD 0
Note that a 0 there does not imply that the device cannot hotplug.
My USB drive reports 0.
-JimC
--
James Cloos cl...@jhcloos.com OpenPGP: 1024D/ED7DAEA6
On Mon, 2012-05-14 at 12:31 -0400, James Cloos wrote:
WD cat /sys/block/sda/removable
WD 0
Note that a 0 there does not imply that the device cannot hotplug.
My USB drive reports 0.
And I'm sure it works fine with udev?
Those who do not understand udev are condemned to reinvent it,
On 5/14/2012 11:17 AM, Pacho Ramos wrote:
Would be too difficult to finally fix ebuilds to properly convet
shebangs and so and then, be able to have a proper system even when
python3 is main interpreter?
Yeah, python_convert_shebangs is an easy fix for most cases.
Personally, I run with it
On 05/14/2012 06:13 PM, Alexandre Rostovtsev wrote:
On Mon, 2012-05-14 at 17:44 +0200, hasufell wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And
On Mon, 14 May 2012 12:56:39 -0400
Olivier Crête tes...@gentoo.org wrote:
On Mon, 2012-05-14 at 12:31 -0400, James Cloos wrote:
WD cat /sys/block/sda/removable
WD 0
Note that a 0 there does not imply that the device cannot hotplug.
My USB drive reports 0.
And I'm sure it works
On 5/13/2012 4:27 PM, Mike Gilbert wrote:
To make ebuilds utilizing python-distutils-ng.eclass usable
out-of-the-box, the python team would like to add the following to
make.defaults in the base profile.
PYTHON_TARGETS=python2_7
See also bug 415575 [1].
Any objections?
Seeing no
On Mon, May 14, 2012 at 12:31:25PM -0400, James Cloos wrote
WD cat /sys/block/sda/removable
WD 0
Note that a 0 there does not imply that the device cannot hotplug.
My USB drive reports 0.
You're right. Same for me. Thanks for pointing it out.
--
Walter Dnes waltd...@waltdnes.org
I propose adding the following global USE flag:
jit - Enable just-in-time compilation for improved performance. May
prevent use of some PaX memory protection features in Gentoo Hardened.
Current local flags that could probably be unified:
app-arch/libzpaq:jit - Enable just-in-time compilation
On Monday 14 May 2012 14:05:12 Alexandre Rostovtsev wrote:
I propose adding the following global USE flag:
jit - Enable just-in-time compilation for improved performance. May
prevent use of some PaX memory protection features in Gentoo Hardened.
Current local flags that could probably be
On Sun, May 13, 2012 at 9:14 AM, Jeroen Roovers j...@gentoo.org wrote:
On Fri, 11 May 2012 16:19:33 -0700
Sébastien Fabbro bicat...@gentoo.org wrote:
dev-lang/icc
dev-lang/ifc
they have up-to-date versions in the science overlay.
Do these up-to-date ebuilds fix the Macrovision bug[1]? Do
On Mon, 14 May 2012 18:01:22 +0200
Chí-Thanh Christopher Nguyễn chith...@gentoo.org wrote:
-Werror is basically saying that it is not safe to ship code which
produces warnings.
An upstream demanding -Werror should work means upstream would need to
test rather a lot more than their own
On Mon, 14 May 2012 17:44:17 +0200
hasufell hasuf...@gentoo.org wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in devmanual or
howtos) how to handle Werror.
Is there a common opinion on that. And shouldn't we add that to the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/05/12 09:54, Olivier Crête wrote:
Hi,
On Thu, 2012-05-10 at 06:34 +0200, Fabio Erculiani wrote:
I think expressing my own opinion about Lennart-made software is my
right, after all.
I would express my opinion about Fabio made software,
El lun, 14-05-2012 a las 20:09 +0200, Agostino Sarubbo escribió:
On Monday 14 May 2012 14:05:12 Alexandre Rostovtsev wrote:
I propose adding the following global USE flag:
jit - Enable just-in-time compilation for improved performance. May
prevent use of some PaX memory protection
El lun, 14-05-2012 a las 20:24 +0200, Jeroen Roovers escribió:
On Mon, 14 May 2012 18:01:22 +0200
Chí-Thanh Christopher Nguyễn chith...@gentoo.org wrote:
-Werror is basically saying that it is not safe to ship code which
produces warnings.
An upstream demanding -Werror should work means
El dom, 06-05-2012 a las 18:38 +0200, Michael Weber escribió:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/06/2012 05:35 PM, Pacho Ramos wrote:
Well, in tree versions are still buggy and outdated, I would vote
for either: 1. Mask them for removal (server is already hardmasked,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 05/14/2012 06:03 PM, hasufell wrote:
On 05/14/2012 06:13 PM, Alexandre Rostovtsev wrote:
On Mon, 2012-05-14 at 17:44 +0200, hasufell wrote:
https://bugs.gentoo.org/show_bug.cgi?id=260867
However, I don't see references to ebuild policy (in
On Mon, May 14, 2012 at 8:05 PM, Alexandre Rostovtsev
tetrom...@gentoo.org wrote:
media-sound/csound:luajit - Use the lua just-in-time compiler
dev-lang/luajit instead of dev-lang/lua
www-client/luakit:luajit - Use the lua just-in-time compiler
dev-lang/luajit instead of dev-lang/lua, which
On Mon, May 14, 2012 at 9:05 PM, Alexandre Rostovtsev
tetrom...@gentoo.org wrote:
Current local flags that could probably be unified:
What about USE=orc? It's JIT in a sense — IIRC, it creates an
executable in /tmp at run-time.
--
Maxim Kammerer
Liberté Linux (discussion / support:
Jeroen Roovers schrieb:
-Werror is basically saying that it is not safe to ship code which
produces warnings.
An upstream demanding -Werror should work means upstream would need to
test rather a lot more than their own favourite
distro/architecture/library versions/kernel/userland, which
On Tue, May 15, 2012 at 1:52 AM, Maxim Kammerer m...@dee.su wrote:
On Mon, May 14, 2012 at 9:05 PM, Alexandre Rostovtsev
tetrom...@gentoo.org wrote:
Current local flags that could probably be unified:
What about USE=orc? It's JIT in a sense — IIRC, it creates an
executable in /tmp at
On Mon, 2012-05-14 at 21:51 +0200, Dirkjan Ochtman wrote:
On Mon, May 14, 2012 at 8:05 PM, Alexandre Rostovtsev
tetrom...@gentoo.org wrote:
media-sound/csound:luajit - Use the lua just-in-time compiler
dev-lang/luajit instead of dev-lang/lua
www-client/luakit:luajit - Use the lua
AR == Alexandre Rostovtsev tetrom...@gentoo.org writes:
AR www-servers/nginx:pcre-jit - Enable JIT for pcre
This one also should remain un-unified. There may be other, unrelated
jit options in the future, whether affecting nginx itself or potential
PDEPENDs or ???.
-JimC
--
James Cloos
My USB drive reports 0.
WD You're right. Same for me. Thanks for pointing it out.
The removable flag specifies whether the drive has removable media;
before flash drives only things like floppy, optical, zip, etc drives
had removable==1. It also would be accurate for flash card readers.
If
OC == Olivier Crête tes...@gentoo.org writes:
OC And I'm sure it works fine with udev?
It automounts when plugged in, if that is what you mean. (In fact each
partition does; the one in fstab(5) where it should and the one not in
fstab in a mount point based on its label.)
And the dev files
On 14/05/12 23:42, Chí-Thanh Christopher Nguyễn wrote:
I personally think that if an upstream says that no warnings must be
produced by the code, and a developer should look at them before
declaring any warnings safe, then that is best followed.
Upstream does not need to take into account
On Mon, May 14, 2012 at 12:09:23PM -0400, Mike Frysinger wrote:
On Monday 14 May 2012 03:53:53 Walter Dnes wrote:
My question... is this API stable or deprecated? I.e. can I count on
it being around for a while? I figure this question is a developer type
question rather than ordinary
On Mon, May 14, 2012 at 03:53:53AM -0400, Walter Dnes wrote:
After some Google-searching, I think I've figured out how to implement
automounting under mdev. I'd like to put in as much sanity-checking
into the script as possible. Right now I have 1 USB stick plugged in as
/dev/sdb. Th hard
On Tue, May 15, 2012 at 4:23 AM, Greg KH gre...@gentoo.org wrote:
We learned that this is not a good idea at all, and should be left to
userspace helper applications
that listen for dbus messages.
Could you perhaps expand a bit on those reasons? E.g., I had good
experience with the following
On Mon, May 14, 2012 at 06:23:36PM -0700, Greg KH wrote:
Actually with all the hype about mdev these days, why not just use a 3
year old version of udev (or maybe 4), that is probably what mdev is at
as far as functionality goes. Why not just fork udev from then and go
forward from that?
On Tue, May 15, 2012 at 04:56:15AM +0300, Maxim Kammerer wrote
I don't know at what state udev was 3 or 4 years ago, but mdev can:
1. Populate /dev (now unnecessary due to devtmpfs).
2. Handle ownership, permissions and symlinks to /dev nodes once they
appear, according to simple rules (can
On Mon, May 14, 2012 at 06:23:36PM -0700, Greg KH wrote
So you need to implement stuff such that you are not dependant on the
bus type. If you see a new disk, act on it, it's that simple.
But note, please do not be automounting disks from uevents directly.
After some more
On 05/11/2012 06:39 PM, Mike Frysinger wrote:
+multijob_child_init() {
+ trap 'echo ${BASHPID} $? '${mj_control_fd} EXIT
+ trap 'exit 1' INT TERM
+}
Just wondering why $! in parent isn't used anywhere, even not for some
integrity check if the child's BASHPID actually was forked by
On 05/14/2012 12:33 AM, Michael Haubenwallner wrote:
+multijob_post_fork() {
+: $(( ++mj_num_jobs ))
+if [[ ${mj_num_jobs} -ge ${mj_max_jobs} ]] ; then
+multijob_finish_one
Feels like ignoring this child's exitstatus isn't intentional here.
Thanks, fixed now:
On Monday 14 May 2012 03:33:58 Michael Haubenwallner wrote:
On 05/11/2012 06:39 PM, Mike Frysinger wrote:
+multijob_child_init() {
+ trap 'echo ${BASHPID} $? '${mj_control_fd} EXIT
+ trap 'exit 1' INT TERM
+}
Just wondering why $! in parent isn't used anywhere, even not for some
On Monday 14 May 2012 13:37:40 Mike Frysinger wrote:
On Monday 14 May 2012 04:44:12 Zac Medico wrote:
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=b4fb
a3 e9fa2e285244de491f57700978158c1838
should really fix it to make the code parallel safe rather than disabling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/14/2012 11:53 AM, Mike Frysinger wrote:
On Monday 14 May 2012 13:37:40 Mike Frysinger wrote:
On Monday 14 May 2012 04:44:12 Zac Medico wrote:
http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=b4fb
a3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/14/2012 12:02 PM, Zac Medico wrote:
On 05/14/2012 11:53 AM, Mike Frysinger wrote:
On Monday 14 May 2012 13:37:40 Mike Frysinger wrote:
On Monday 14 May 2012 04:44:12 Zac Medico wrote:
On 05/14/2012 01:10 PM, Mike Frysinger wrote:
On Monday 14 May 2012 15:08:32 Zac Medico wrote:
Actually, the inode_var_name thing will not work unless it's all in
one process.
hmm, true, but that's the level we currently parallelize at, so it's fine.
we
do one subprocess per ELF and
On Monday 14 May 2012 18:42:07 Zac Medico wrote:
On 05/14/2012 01:10 PM, Mike Frysinger wrote:
On Monday 14 May 2012 15:08:32 Zac Medico wrote:
Actually, the inode_var_name thing will not work unless it's all in
one process.
hmm, true, but that's the level we currently parallelize at,
51 matches
Mail list logo
