On Wed, 29 May 2013 19:22:32 -0500
William Hubbs wrote:
> We could probably also turn gcc-config into an eselect module if we
> want to use that argument.
Someone did, but unfortunately gcc-config is a big pile of poorly
understood voodoo, so eclectic gcc ended up being abandoned.
--
Ciaran McC
On Wed, 29 May 2013 19:22:32 -0500
William Hubbs wrote:
> > For the same reason we have all the other eselect modules.
>
> We could probably also turn gcc-config into an eselect module if we
> want to use that argument.
Looking at Duncan's reply, that has already happened in the past.
Really,
Tom Wijsman wrote:
> For the same reason we have all the other eselect modules.
> http://www.gentoo.org/proj/en/eselect/
Ironically, that project description even mentions init system... :)
As someone else pointed out, not the same thing. Quoting:
William Hubbs wrote:
> Yes, but the init syste
On Wed, 29 May 2013 22:52:58 -0400
"Walter Dnes" wrote:
> If users can already do it themselves, then why this entire thread?
> Why do we need eselect/whatever?
The big argument in favour of eselect is that when the procedure for
switching things changes, there's no need to worry about users do
On 05/29/2013 10:55 PM, William Hubbs wrote:
> On Wed, May 29, 2013 at 09:56:00PM +0200, Tom Wijsman wrote:
>>> There are a couple of other possible approaches...
>>>
>>> 1) If the 2 systems can achieve peacefull co-existance (i.e. no
>>> identically-named files with different contents) then simply
On Wed, 29 May 2013 22:52:58 -0400
"Walter Dnes" wrote:
> > > In order for a different init system to come up, some file(s)
> > > somewhere *MUST* be different, no ifs/ands/ors/buts.
> >
> > How true is this in general? It is usually only a change of the init
> > parameter.
>
> Where is the ini
On Wed, May 29, 2013 at 09:56:00PM +0200, Tom Wijsman wrote
> "Walter Dnes" wrote:
>
> > In order for a different init system to come up, some file(s)
> > somewhere *MUST* be different, no ifs/ands/ors/buts.
>
> How true is this in general? It is usually only a change of the init
> parameter.
William Hubbs posted on Wed, 29 May 2013 19:22:32 -0500 as excerpted:
> We could probably also turn gcc-config into an eselect module if we want
> to use that argument.
IIRC it actually was, at one point. The eselect gcc module even allowed
separate configs for 32-bit and 64-bit on at least amd
On Thu, May 30, 2013 at 02:06:42AM +0200, Tom Wijsman wrote:
> On Wed, 29 May 2013 15:55:23 -0500
> William Hubbs wrote:
>
> > > We want to make this easier towards the user, therefore doing heavy
> > > discussion to exhaust all the alternatives and maybe someone's
> > > interested in implementin
On Wed, 29 May 2013 15:55:23 -0500
William Hubbs wrote:
> > We want to make this easier towards the user, therefore doing heavy
> > discussion to exhaust all the alternatives and maybe someone's
> > interested in implementing one of them that appears most feasible.
>
> Since users can already do
El mié, 29-05-2013 a las 11:46 -0400, Ian Stakenvicius escribió:
> On 29/05/13 11:43 AM, Vadim A. Misbakh-Soloviov wrote:
> > I think, it'll be nice to have a way to suggest some packages to
> > user, when (s)he installs something. For now it is only way to do
> > that by something like:
> >
> > p
On Wed, May 29, 2013 at 09:56:00PM +0200, Tom Wijsman wrote:
> > There are a couple of other possible approaches...
> >
> > 1) If the 2 systems can achieve peacefull co-existance (i.e. no
> > identically-named files with different contents) then simply have 2
> > boot entries in /etc/lilo.conf (or
On Wed, 29 May 2013 14:15:54 -0400
"Walter Dnes" wrote:
> In order for a different init system to come up, some file(s)
> somewhere *MUST* be different, no ifs/ands/ors/buts.
How true is this in general? It is usually only a change of the init
parameter. As far as I heard there is only one excep
On Wed, May 29, 2013 at 10:52:49AM +0200, Tom Wijsman wrote
> On Wed, 29 May 2013 00:36:58 + (UTC)
> Duncan <1i5t5.dun...@cox.net> wrote:
>
> > 3b) Except... at that point root isn't writable
>
> Let me stop you here. Does it need to be writable at that point?
>
> We're reading the path of t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 29/05/13 11:43 AM, Vadim A. Misbakh-Soloviov wrote:
> I think, it'll be nice to have a way to suggest some packages to
> user, when (s)he installs something. For now it is only way to do
> that by something like:
>
> pkg_postinst() { if ! has_ver
I think, it'll be nice to have a way to suggest some packages to user,
when (s)he installs something. For now it is only way to do that by
something like:
pkg_postinst() {
if ! has_version dev-lua/iluajit; then
einfo "You'd probably want to install dev-lua/iluajit to";
On 30/05/2013 01:06, hasufell wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/29/2013 04:51 PM, Michael Palimaka wrote:
Would it be possible to add repoman checks for this, and other
common failures like missing PYTHON_USEDEP?
The latter is impossible. Repoman has no way to figur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/29/2013 04:51 PM, Michael Palimaka wrote:
> Would it be possible to add repoman checks for this, and other
> common failures like missing PYTHON_USEDEP?
>
>
The latter is impossible. Repoman has no way to figure out if
PYTHON_USEDEP is necessa
On 28/05/2013 01:35, Jonathan Callen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
A quick reminder for anyone using python-r1.eclass or
python-single-r1.eclass:
These eclasses provide a ${PYTHON_REQUIRED_USE} variable that should
be included in REQUIRED_USE under the same USE conditio
On 29/05/2013 21:18, Alexey Shvetsov wrote:
Yep I'm thinking about gerrit like workflow. But seems it doesnt make sense
with RB and CVS.
Yes, Review Board and Gerrit target different things.
Yep I'm thinking about gerrit like workflow. But seems it doesnt make sense
with RB and CVS.
В письме от 29 мая 2013 10:22:29 пользователь Tomáš Chvátal написал:
> He is probably thinking about buildtests and automatic commit merges which
> are not possible with reviewboard.
>
> Dne 29.5.2013 9:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/20/2013 08:29 PM, Tom Wijsman wrote:
> We have `iamlate` for this in app-portage/gentoolkit-dev.
/usr/bin/imlate , nice ;-)
- --
Michael Weber
Gentoo Developer
web: https://xmw.de/
mailto: Michael Weber
-BEGIN PGP SIGNATURE-
Version
On Wed, 29 May 2013 00:36:58 + (UTC)
Duncan <1i5t5.dun...@cox.net> wrote:
> 3b) Except... at that point root isn't writable
Let me stop you here. Does it need to be writable at that point?
We're reading the path of the init file to boot from a file, we start
the executable at that path; no w
He is probably thinking about buildtests and automatic commit merges which
are not possible with reviewboard.
Dne 29.5.2013 9:09 "Michael Palimaka" napsal(a):
> On 29/05/2013 02:07, Alexey Shvetsov wrote:
>
>> Hi!
>>
>> Cool! I didnt use RB before, but i use gerrit. Do you pan to integrate it
>>
On 29/05/2013 02:07, Alexey Shvetsov wrote:
Hi!
Cool! I didnt use RB before, but i use gerrit. Do you pan to integrate it to
g.o.g.o? It seems can be done by git commit hooks
What sort of integration did you have in mind?
25 matches
Mail list logo
