Hey, just a heads up as a user. I'm currently using LXDE.
On Sun, Aug 7, 2016 at 1:22 AM, Pacho Ramos wrote:
> Now https://wiki.gentoo.org/wiki/Project:LXDE is empty
>
> Feel free to join, anyway, if I don't misremember, LXDE is dead for a
> long time in favor of LXQT... in that case treecleani
On 10/08/16 06:08, Michał Górny wrote:
> On Wed, 10 Aug 2016 01:52:29 +0100
> "M. J. Everitt" wrote:
>
>> On 10/08/16 01:39, Lei Zhang wrote:
>>> 2016-08-09 13:58 GMT+08:00 Fabian Groffen :
As a question to Lei, I'm wondering why you chose eselect compiler, and
not gcc-config to manage t
On Wed, 10 Aug 2016 01:52:29 +0100
"M. J. Everitt" wrote:
> On 10/08/16 01:39, Lei Zhang wrote:
> > 2016-08-09 13:58 GMT+08:00 Fabian Groffen :
> >> As a question to Lei, I'm wondering why you chose eselect compiler, and
> >> not gcc-config to manage the links. In a way, gcc-config is tailored
>
Lei Zhang writes:
> I'm just afraid gcc-config would become too complex that way, so I
> prefer a simpler approach: let eselect-compiler be version-agnostic.
> Then we can have clang-config to handle the versioning of clang,
> icc-config to handle icc, etc.
If we model after eselect python here,
2016-08-10 0:16 GMT+08:00 Zac Medico :
> I'm guessing you Darwin folks don't compile many Linux kernels? The last
> I heard, clang is not yet a drop-in replacement for gcc when building
> the Linux kernel:
>
> http://llvm.linuxfoundation.org/index.php/Main_Page
Yes, Linux kernel has to be buil
On 10/08/16 01:39, Lei Zhang wrote:
> 2016-08-09 13:58 GMT+08:00 Fabian Groffen :
>> As a question to Lei, I'm wondering why you chose eselect compiler, and
>> not gcc-config to manage the links. In a way, gcc-config is tailored
>> towards gcc, but it does a lot of things also for the environment.
2016-08-09 13:58 GMT+08:00 Fabian Groffen :
> As a question to Lei, I'm wondering why you chose eselect compiler, and
> not gcc-config to manage the links. In a way, gcc-config is tailored
> towards gcc, but it does a lot of things also for the environment. With
> clang, from my experience, you j
On 08/08/2016 10:58 PM, Fabian Groffen wrote:
> On 08-08-2016 13:45:07 -0500, R0b0t1 wrote:
>> On Mon, Aug 8, 2016 at 11:23 AM, Lei Zhang wrote:
>>> "cc" is the standard C compiler name defined in POSIX, so ideally any
>>> gcc-agnostic programs should use "cc" instead of "gcc". Practically,
>>> bu
On 08/09/2016 12:58 AM, Fabian Groffen wrote:
On 08-08-2016 13:45:07 -0500, R0b0t1 wrote:
On Mon, Aug 8, 2016 at 11:23 AM, Lei Zhang wrote:
"cc" is the standard C compiler name defined in POSIX, so ideally any
gcc-agnostic programs should use "cc" instead of "gcc". Practically,
build tools lik
