On 14/12/16 12:29, Fabian Groffen wrote:
> On 14-12-2016 13:01:16 -0500, Doug Freed wrote:
>> On Wed, Dec 14, 2016 at 12:48 PM, Nathan Zachary
>> wrote:
>>> On 14/12/16 10:11, Doug Freed wrote:
>>>>> I somehow doubt that would give me the expected number onl
On 14/12/16 10:11, Doug Freed wrote:
> On Wed, Dec 14, 2016 at 11:04 AM, Michał Górny wrote:
>> On Wed, 14 Dec 2016 15:27:25 +0300
>> Andrew Savchenko wrote:
>>
>>> On Tue, 13 Dec 2016 10:36:15 +0100 Michał Górny wrote:
+ nproc=$(python -c 'import multiprocessing;
print(multi
replacement options, with a
> wee bit of migration detail
>
>
> hth,
> James
>
I was under the impression that both LXDE and LXQT would continue
development, but that LXQT would be favoured. Is there an official
statement that LXDE is dead?
Cheers,
Nathan Zachary
signature.asc
Description: OpenPGP digital signature
of NOT using GitHub. Though it is a great
resource, I second the idea that Gentoo should offer the repository
space in order to stay separate.
Cheers,
Nathan Zachary
signature.asc
Description: OpenPGP digital signature
dex.php/Archboot ..
> looks like a potentially safer bet ?
>
+1. Arch would probably be the best choice for a systemd-based rescue disc.
Cheers,
Nathan Zachary
lved. Please
try to focus on the points raised by other developers and users, so
that the end result is something that benefits the community and
distribution as a whole.
Cheers,
Nathan Zachary
n production
environments, it is likely better to provide users with ample warning
than to risk the application failing and troubleshooting thereafter.
Cheers,
Nathan Zachary
On 24/08/10 22:21, Joshua Saddler wrote:
On Tue, 24 Aug 2010 19:18:56 +0200
Christian Faulhammer wrote:
Hi,
Joshua Saddler:
The big issue with the docs is that IF OpenRC/baselayout-2 are marked
stable, it will require massive changes to hundreds of our other doc
files.
Is there a list of
On 05/04/10 13:12, Ben de Groot wrote:
> After the mostly positive feedback on the recent wiki discussion, we
> have now gone ahead, formed a preliminary team consisting of both
> users and developers, and put up a project page [1]. All constructive
> feedback on this new project is welcome.
>
> We
On 05/04/10 11:07, Jon Portnoy wrote:
> On Mon, Apr 05, 2010 at 08:50:49AM +0300, Eray Aslan wrote:
>
>> Just replying randomly.
>>
>> On 05.04.2010 04:33, Tobias Heinlein wrote:
>>
>>> I think this is a good starting point to get rid of the "some important
>>> questions are too hard to ans
just sign up and use
> immediately). This will probably prevent most kinds of spam and allow
> for much better tracking of editing and history, allow for banning,
> etc. without closing the wiki up too much.
> Also, from what I could tell, this is how others are managing their
> wiki as well (Arch and Amarok, for example).
>
> Dror Levin
>
>
I would enjoy working on a wiki as well as the fora, so I'm volunteering
as well.
--Nathan Zachary
not currently
doing ebuild work, but I think this idea could really help out the
status of the tree. Attached to it could be a stabilisation day as well.
--Nathan Zachary
systems run desktop
>>>> environments without needing printing support. As we advance further
>>>> toward a paperless computing experience, the need for printing
>>>> support becomes even less. And, as it is incredibly simple to add
>>>> print
le to add
>> print capabilities by placing the cups USE flag in /etc/make.conf,
>> that choice should be left to the user.
>>
>> Regards,
>> Nathan Zachary
>
> One could argue the opposite as well. Adding -cups to make.conf is
> just as easy.
>
> I&
le. Many systems run desktop environments
without needing printing support. As we advance further toward a
paperless computing experience, the need for printing support becomes
even less. And, as it is incredibly simple to add print capabilities by
placing the cups USE flag in /etc/make.conf, that choice should be left
to the user.
Regards,
Nathan Zachary
On 02/03/10 13:39, Sebastian Pipping wrote:
> On 03/02/10 20:28, Nathan Zachary wrote:
>
>>> This looks like overkill to me. One keyword should be enough, and for
>>> supplementary information "Status Whiteboard" could be used.
>>>
>>>
On 02/03/10 13:17, Ulrich Mueller wrote:
>> On Tue, 02 Mar 2010, Sebastian Pipping wrote:
>>
>
>> To make naming a bit more consistent, how about:
>> - BUGDAY-CANDIDATE
>> - BUGDAY-ACCEPTED
>> - BUGDAY-REFUSED
>>
>
>> They're a bit long but I think it's worth to not
hiperon wrote:
> Thank you all very much !
>
> I knew it this was a simple case of 'flapping-ears' or 'ears covering
> eyes'. The road now is clear enough. Thank you all again, very much.
> (about the html on the mail, I am terribly sorry I didn't noticed. I
> never do that, but today I am kinda o
oper can then make the ebuild file for you. If I get a little time
today to look at the source, I might be able to throw one together. The
best thing for you to do now though is to file the bug.
Hope that helps,
Nathan Zachary
sk for help from the community in a more direct way.
> Maybe, something like the monthly reminders we get for the council-meeting.
> To back up the fact that lack of content should be a non-issue is the
> following excerpt from the thread i mentioned:
>
> Nathan Zachary
Man Shankar wrote:
> Hi,
>
> Firstly apologies if this is the wrong -list for such a post. I would
> like to see the GWN restart (i m sure i m not the only one) ! Infact i
> can contribute my weekends to it. That should be enough time.
>
> As regards, the need for a newsletter, i guess its more to
y be necessary to manually uninstall packages that no longer
exist in the portage tree since it may not be possible to satisfy their
dependencies. Also, be aware of the --with-bdeps option that is documented
in `man emerge`.
Thanks for the information Josh.
Josh Saddler wrote:
> Nathan Zacha
If one has built a system with the default python and perl USE flags,
what steps would be necessary to remove all packages and dependencies
after removing them from the USE declarations?
Jorge Manuel B. S. Vicetto wrote:
> Dawid WgliDski wrote:
> > On Monday 08 of December 2008 11:34:21 Maciej Mr
23 matches
Mail list logo
