At Freitag, 12. November 2010 02:26 Alex Matviychuk wrote:
> This is from a Linux From Scratch readme here:
> http://www.linuxfromscratch.org/hints/downloads/files/dcron.txt
I would prefer this info:
http://www.gentoo.org/doc/en/cron-guide.xml
Here you can see that dcron is the first option in
On 11/12/10 01:51, Auguste Pop wrote:
...
I hope python3 won't die this way, so that all the previous efforts in
transition to python3 will not go in vain. Maybe we just took the
transitional leap too early when nobody is ready except us.
As you note, "nobody is ready except us" -- we are ready
Hi,
Firstly, I want to state clearly that I am 100% supportive to the
python3 transition which took part in Archlinux a month ago.
I installed libreoffice from extra today to replace go-openoffice. And
all of a sudden, python is no longer required by any package at all. I
checked the dependencies
On Fri, 2010-11-12 at 13:46 +0800, Gergely Imreh wrote:
> On 12 November 2010 13:32, David C. Rankin
> wrote:
> > Guys,
> >
> >I'm using yum-createrepo 0.9.8-3 on from AUR and suddenly my
> > createrepo updates
> > on my Arch server are failing with the following error:
> >
> > 23:22 nirv
On 12 November 2010 13:32, David C. Rankin
wrote:
> Guys,
>
> I'm using yum-createrepo 0.9.8-3 on from AUR and suddenly my
> createrepo updates
> on my Arch server are failing with the following error:
>
> 23:22 nirvana:/home/backup/rpms> sudo createrepo --update -d openSUSE_11.3/
> File
Guys,
I'm using yum-createrepo 0.9.8-3 on from AUR and suddenly my createrepo
updates
on my Arch server are failing with the following error:
23:22 nirvana:/home/backup/rpms> sudo createrepo --update -d openSUSE_11.3/
File "/usr/share/createrepo/genpkgmetadata.py", line 189
print t
Am Fri, 12 Nov 2010 13:10:12 +0900
schrieb Alex Matviychuk :
> I agree, however, it sounds a bit odd to say that we should replace a
> simple package with a more complicated one in the hope the more
> complicated one will screw us over less going forward. We're just as
> bound to the idiosyncrasie
On Fri, Nov 12, 2010 at 13:10, Alex Matviychuk wrote:
> For such a crucial system package it would seem wise to deal with the
> devil that's easier to understand (in theory, I don't claim to
> understand the internals of e.
That should read:
For such a crucial system package it would seem wise t
On Fri, Nov 12, 2010 at 11:57, Loui Chang wrote:
> The only problem is finding someone who can do the work to maintain
> dcron. It's pretty damning to have a scheduler that can't schedule
> properly installed by default - that's what people seem to be concerned
> about mostly. I'd like to keep the
On 11/11/10 20:26, Alex Matviychuk wrote:
Thanks to this thread I decided to look at both dcron and fcron. First
google result for dcron led me to this:
(As Loui noted, many of those points are changed by the passage of seven
years. Distros probably use different crons now; and fcron has impro
On Fri 12 Nov 2010 10:26 +0900, Alex Matviychuk wrote:
> Thanks to this thread I decided to look at both dcron and fcron. First
> google result for dcron led me to this:
>
> This is from a Linux From Scratch readme here:
> http://www.linuxfromscratch.org/hints/downloads/files/dcron.txt
Nice. The g
Thanks to this thread I decided to look at both dcron and fcron. First
google result for dcron led me to this:
1 Why use dcron when there's fcron?
---
- dcron is SIMPLE:
dcron just gives you two binaries, crond and crontab, and consists
only of a few
On 11.11.2010 23:50, Ng Oon-Ee wrote:
> On Thu, 2010-11-11 at 16:31 -0500, Leonid Isaev wrote:
>> Not only this, but also the fact that now there are 2 crons being maintained:
>> fcron in community and dcron in core. Removing dcron to, say, AUR, will be a
>> wiser use of devs' time...
> Bottom-post
On Thu, 2010-11-11 at 16:31 -0500, Leonid Isaev wrote:
> Not only this, but also the fact that now there are 2 crons being maintained:
> fcron in community and dcron in core. Removing dcron to, say, AUR, will be a
> wiser use of devs' time...
Bottom-posting please. And I don't see a problem with t
Not only this, but also the fact that now there are 2 crons being maintained:
fcron in community and dcron in core. Removing dcron to, say, AUR, will be a
wiser use of devs' time...
On (11/11/10 21:35), Sven-Hendrik Haase wrote:
-~> On 11.11.2010 21:15, Attila wrote:
-~> The way I see it we at lea
On 11.11.2010 21:15, Attila wrote:
> At Donnerstag, 11. November 2010 20:16 Sven-Hendrik Haase wrote:
>
>> So, not a mail since a while. Can we replace dcron now? :)
> What i don't understand is this "replace" here because fcron (or incron) is
> only
> one "pacman -S" away. And i say this as
At Donnerstag, 11. November 2010 20:16 Sven-Hendrik Haase wrote:
> So, not a mail since a while. Can we replace dcron now? :)
What i don't understand is this "replace" here because fcron (or incron) is
only
one "pacman -S" away. And i say this as an fcron user. :)
See you, Attila
On 09.11.2010 11:47, Dieter Plaetinck wrote:
> FWIW:
> I've gone through the archives and found multiple threads about our
> cron discussions.
> http://mailman.archlinux.org/pipermail/arch-dev-public/2009-September/
> http://mailman.archlinux.org/pipermail/arch-dev-public/2010-January
> (esp.
> htt
18 matches
Mail list logo
