El lun, 15-04-2013 a las 07:21 +0200, Michał Górny escribió:
> On Sun, 14 Apr 2013 23:22:04 +0200
> Pacho Ramos wrote:
>
> > I noticed this problem now that joe was modified to comply with this
> > rule set in devmanual:
> > http://devmanual.gentoo.org/ebuild-writing/file-format/index.html#indent
On Sun, 14 Apr 2013 23:22:04 +0200
Pacho Ramos wrote:
> I noticed this problem now that joe was modified to comply with this
> rule set in devmanual:
> http://devmanual.gentoo.org/ebuild-writing/file-format/index.html#indenting-and-whitespace
>
> It stated a tab represents 4 spaces. Where does t
The attached list notes all of the packages that were added or removed
from the tree, for the week ending 2013-04-14 23h59 UTC.
Removals:
sys-fs/device-mapper2013-04-09 09:50:27 ssuominen
games-engines/gambatte 2013-04-13 21:19:06 hasufell
Additions:
a
> "JR" == Jeroen Roovers writes:
JR> On Fri, 12 Apr 2013 16:08:10 -0400
JR> Mike Frysinger wrote:
>> that you remember. i think it's more likely you copy & pasted some
>> line a long time ago than baselayout modified it for you.
JR> Exactly, but where did that come from?
If it didn't com
> On Sun, 14 Apr 2013, Ciaran McCreesh wrote:
> On Sun, 14 Apr 2013 23:22:04 +0200
> Pacho Ramos wrote:
>> It stated a tab represents 4 spaces. Where does this rule come from?
>> Why 8 spaces wasn't chosen instead? I say that because looks like 8
>> spaces equivalence is used by tools like "c
On 4/2/2013 10:54 AM, Duncan wrote:
Tho in practice, if you're here long you do develop a rather thick hide.
Nothing NEAR what it was a few years ago, tho. Before it gets anywhere
near that, there's warnings, these days.
Kinda just what happens, when you put a bunch of unpaid, sleep-deprived,
On Sun, 14 Apr 2013 23:22:04 +0200
Pacho Ramos wrote:
> I noticed this problem now that joe was modified to comply with this
> rule set in devmanual:
> http://devmanual.gentoo.org/ebuild-writing/file-format/index.html#indenting-and-whitespace
>
> It stated a tab represents 4 spaces. Where does th
I noticed this problem now that joe was modified to comply with this
rule set in devmanual:
http://devmanual.gentoo.org/ebuild-writing/file-format/index.html#indenting-and-whitespace
It stated a tab represents 4 spaces. Where does this rule come from? Why
8 spaces wasn't chosen instead? I say that
On 04/14/2013 02:59 AM, Pacho Ramos wrote:
> El dom, 14-04-2013 a las 11:45 +0200, Michał Górny escribió:
>> On Sun, 14 Apr 2013 11:40:03 +0200
>> Pacho Ramos wrote:
>>
>>> # >=mono-0.92 versions using mcs -pkg:foo-sharp require shared memory, so
>>> we set the
>>> # shared dir to ${T} so that ${
On 04/14/2013 06:09 AM, Rich Freeman wrote:
> Also, I'm sure I've used the portage API in less-than-ideal ways.
> Having not really used it before this was half a learning exercise.
> Feel free to send me suggestions/pointers. If somebody knows of an
> easy way to process metadata in python (short
All,
per lu_zero's request yesterday, OpenRC now has an organization and a
repository on github [1] [2].
For now, we are still using gentoo's bugzilla for bugs, but this should
ease collaboration on the project.
If you want to be added to the team, please email me privately with your
github user
El dom, 14-04-2013 a las 19:15 +0200, Andreas K. Huettel escribió:
> Am Sonntag, 14. April 2013, 12:06:48 schrieb Pacho Ramos:
> >
> > The messages are shown the first time by elog *and* saved
> > in /usr/share/doc/*/README.gentoo, adding the advantage of users having
> > that docs always present
Am Sonntag, 14. April 2013, 12:06:48 schrieb Pacho Ramos:
>
> The messages are shown the first time by elog *and* saved
> in /usr/share/doc/*/README.gentoo, adding the advantage of users having
> that docs always present without needing to re-emerge the package or
> manually read ebuilds
How abou
Am Sonntag, 14. April 2013, 15:09:13 schrieb Rich Freeman:
> For whoever is interested I tossed together a script to identify
> packages that would immediately benefit from slot operator
> dependencies but which are not doing so.
>
> The list can be found at:
> http://dev.gentoo.org/~rich0/misseds
On Sun, 14 Apr 2013 17:39:44 +0100
Ciaran McCreesh wrote:
> On Sun, 14 Apr 2013 16:58:07 +0200
> Michał Górny wrote:
> > On Sun, 14 Apr 2013 15:22:42 +0100
> > Ciaran McCreesh wrote:
> > > On Sat, 13 Apr 2013 23:23:57 +0200
> > > Michał Górny wrote:
> > > > As most of you probably doesn't know
On Sun, 14 Apr 2013 16:58:07 +0200
Michał Górny wrote:
> On Sun, 14 Apr 2013 15:22:42 +0100
> Ciaran McCreesh wrote:
> > On Sat, 13 Apr 2013 23:23:57 +0200
> > Michał Górny wrote:
> > > As most of you probably doesn't know, PMS guarantees that ${D}
> > > always ends with a slash. It seems that t
On 14/04/2013 12:52, Tom Wijsman wrote:
> If people don't agree with this apporach, we may want to solve the
> actual problem in a different manner; one could write `eselect elog`
> just like we have `eselect news`, that would force them to process
> through the log messages and just not simply ign
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Sun, 14 Apr 2013 16:14:57 +0200
hasufell wrote:
> On 04/13/2013 11:23 PM, Michał Górny wrote:
> > Your thoughts?
> >
>
> Sounds ok, but how will the transition happen exactly? Will the
> behavior just change for new EAPIs or for all? If for al
On Sun, 14 Apr 2013 15:22:42 +0100
Ciaran McCreesh wrote:
> On Sat, 13 Apr 2013 23:23:57 +0200
> Michał Górny wrote:
> > As most of you probably doesn't know, PMS guarantees that ${D} always
> > ends with a slash. It seems that this particular wording was enforced
> > by historical portage behav
On Sat, 13 Apr 2013 23:23:57 +0200
Michał Górny wrote:
> As most of you probably doesn't know, PMS guarantees that ${D} always
> ends with a slash. It seems that this particular wording was enforced
> by historical portage behavior (instead of fixing the ebuilds...) yet
> it didn't ever get really
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/13/2013 11:23 PM, Michał Górny wrote:
> Your thoughts?
>
Sounds ok, but how will the transition happen exactly? Will the
behavior just change for new EAPIs or for all? If for all, who will do
the tinderbox run?
-BEGIN PGP SIGNATURE-
Ver
On 14/04/2013 23:09, Rich Freeman wrote:
For whoever is interested I tossed together a script to identify
packages that would immediately benefit from slot operator
dependencies but which are not doing so.
The list can be found at:
http://dev.gentoo.org/~rich0/missedslotops.txt
This was generat
For whoever is interested I tossed together a script to identify
packages that would immediately benefit from slot operator
dependencies but which are not doing so.
The list can be found at:
http://dev.gentoo.org/~rich0/missedslotops.txt
This was generated by:
https://github.com/rich0/finddepslot
On Sun, 14 Apr 2013 13:32:29 +0200
Michał Górny wrote:
> There you can find at least my rough estimates of how many ebuilds
> are directly affected. Shortly saying, if we fix PMS, we need to fix,
> say, 200 ebuilds. If we leave it as is, we have around 1750 obviously
> broken ebuilds + over 3000
On Sat, 13 Apr 2013 23:23:57 +0200
Michał Górny wrote:
> As most of you probably doesn't know, PMS guarantees that ${D} always
> ends with a slash. It seems that this particular wording was enforced
> by historical portage behavior (instead of fixing the ebuilds...) yet
> it didn't ever get reall
Michał Górny wrote:
> > > Any thoughts?
> >
> > If doing this at all I think it should take an -r option to enable
> > the new recursion, for symmetry with the do* functions and for
> > backwards compatibility.
>
> Backwards compatibility with what?
With the old non-recursive behavior of edos2un
On Sun, 14 Apr 2013 12:06:48 +0200
Pacho Ramos wrote:
> The messages are shown the first time by elog *and* saved
> in /usr/share/doc/*/README.gentoo, adding the advantage of users
> having that docs always present without needing to re-emerge the
> package or manually read ebuilds
How are users
On Sun, 14 Apr 2013 12:37:05 +0200
Peter Stuge wrote:
> Michał Górny wrote:
> > Any thoughts?
>
> If doing this at all I think it should take an -r option to enable
> the new recursion, for symmetry with the do* functions and for
> backwards compatibility.
Backwards compatibility with what?
--
On Sun, 14 Apr 2013 12:25:27 +0200
Pacho Ramos wrote:
> El dom, 14-04-2013 a las 12:08 +0200, Michał Górny escribió:
> > On Sun, 14 Apr 2013 11:59:14 +0200
> > Pacho Ramos wrote:
> >
> > > El dom, 14-04-2013 a las 11:45 +0200, Michał Górny escribió:
> > > > On Sun, 14 Apr 2013 11:40:03 +0200
>
Michał Górny wrote:
> Any thoughts?
If doing this at all I think it should take an -r option to enable
the new recursion, for symmetry with the do* functions and for
backwards compatibility.
//Peter
El dom, 14-04-2013 a las 12:08 +0200, Michał Górny escribió:
> On Sun, 14 Apr 2013 11:59:14 +0200
> Pacho Ramos wrote:
>
> > El dom, 14-04-2013 a las 11:45 +0200, Michał Górny escribió:
> > > On Sun, 14 Apr 2013 11:40:03 +0200
> > > Pacho Ramos wrote:
> > >
> > > > # >=mono-0.92 versions using
Michał Górny wrote:
> Your thoughts?
+1
pgp1yo32f0xoD.pgp
Description: PGP signature
On Sun, 14 Apr 2013 11:59:14 +0200
Pacho Ramos wrote:
> El dom, 14-04-2013 a las 11:45 +0200, Michał Górny escribió:
> > On Sun, 14 Apr 2013 11:40:03 +0200
> > Pacho Ramos wrote:
> >
> > > # >=mono-0.92 versions using mcs -pkg:foo-sharp require shared memory, so
> > > we set the
> > > # shared
El dom, 14-04-2013 a las 04:08 -0600, Ryan Hill escribió:
> On Sun, 14 Apr 2013 10:23:00 +0200
> "Andreas K. Huettel" wrote:
>
> > Am Sonntag, 14. April 2013, 10:24:18 schrieb Ryan Hill:
> > >
> > > Personally I think that the entire idea of only displaying messages on the
> > > first install is
El dom, 14-04-2013 a las 11:45 +0200, Michał Górny escribió:
> On Sun, 14 Apr 2013 11:40:03 +0200
> Pacho Ramos wrote:
>
> > # >=mono-0.92 versions using mcs -pkg:foo-sharp require shared memory, so
> > we set the
> > # shared dir to ${T} so that ${T}/.wapi can be used during the install
> > pr
El dom, 14-04-2013 a las 11:45 +0200, Michał Górny escribió:
> On Sun, 14 Apr 2013 11:40:03 +0200
> Pacho Ramos wrote:
>
> > # >=mono-0.92 versions using mcs -pkg:foo-sharp require shared memory, so
> > we set the
> > # shared dir to ${T} so that ${T}/.wapi can be used during the install
> > pr
On Sun, 14 Apr 2013 10:23:00 +0200
"Andreas K. Huettel" wrote:
> Am Sonntag, 14. April 2013, 10:24:18 schrieb Ryan Hill:
> >
> > Personally I think that the entire idea of only displaying messages on the
> > first install is completely asinine. What exactly is the benefit? Were
> > users compla
On Sun, 14 Apr 2013 11:40:03 +0200
Pacho Ramos wrote:
> # >=mono-0.92 versions using mcs -pkg:foo-sharp require shared memory, so we
> set the
> # shared dir to ${T} so that ${T}/.wapi can be used during the install
> process.
> export MONO_SHARED_DIR="${T}"
Don't use ${T} in global scope. And
Due reasons explained here:
https://bugs.gentoo.org/show_bug.cgi?id=462052#c1
We would like to start a process of simplifying dotnet maintained
eclasses a lot because they are currently really hard to maintain. As a
start point, we will need a simple eclass simply to export some
variables needed t
El dom, 14-04-2013 a las 02:24 -0600, Ryan Hill escribió:
> On Sun, 14 Apr 2013 08:55:39 +0200
> Tom Wijsman wrote:
>
> > On Sat, 13 Apr 2013 23:09:05 -0600
> > Ryan Hill wrote:
> > >
> > > > - Make use of readme.gentoo.eclass to make the user aware of the
> > > > Gentoo Linux Kernel Upgrade G
El dom, 14-04-2013 a las 08:55 +0200, Tom Wijsman escribió:
> On Sat, 13 Apr 2013 23:09:05 -0600
> Ryan Hill wrote:
> >
> > > - Make use of readme.gentoo.eclass to make the user aware of the
> > > Gentoo Linux Kernel Upgrade Guide only the first time he emerges
> > > the package. Fixes bug #45
On 4/13/2013 2:23 PM, Michał Górny wrote:
Your thoughts?
+1, this causes untold agonies for my pet platform. See #465772 for
more thorough griping :)
-gmt
On 4/13/2013 9:56 PM, Ryan Hill wrote:
On Fri, 12 Apr 2013 13:04:57 -0700
"Gregory M. Turner" wrote:
What do people think of something like this? Obviously the equivalent
patch to prefix would need to include a test for
PREFIX_DISABLE_GEN_USR_LDSCRIPT:
Author: Gregory M. Turner
Date: Fri
Am Sonntag, 14. April 2013, 10:24:18 schrieb Ryan Hill:
>
> Personally I think that the entire idea of only displaying messages on the
> first install is completely asinine. What exactly is the benefit? Were
> users complaining that we were being too helpful and they'd like us to
> hide important
On Sun, 14 Apr 2013 08:55:39 +0200
Tom Wijsman wrote:
> On Sat, 13 Apr 2013 23:09:05 -0600
> Ryan Hill wrote:
> >
> > > - Make use of readme.gentoo.eclass to make the user aware of the
> > > Gentoo Linux Kernel Upgrade Guide only the first time he emerges
> > > the package. Fixes bug #457598
45 matches
Mail list logo
