public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Please rework  next commit 23b810171806939a23c3d5df7758b90dda357116 !!!
Date: Thu, 10 Jul 2014 17:15:40 +0200	[thread overview]
Message-ID: <1405005340.16965.45.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <0cde70725c7927fd52400d67655f2dca@mail01.ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1297 bytes --]

Hi Arne,

I don't quite agree with this. I think the commit is find and modifies a
system configuration file that is not modified in any manner by the web
interface or any other script.

Users that put their own modifications into those files will sooner or
later crash their systems any way. That is why we usually include files
where they can put their own modifications. I find it always incredibly
unnecessary to go through this procedure for crontab just because some
users cannot create their own one. The process is faulty and takes a lot
of time to do.

I don't insist on keeping this commit in the repository, so if you
insist on inserting it on the fly I will do that instead.

-Michael

On Thu, 2014-07-10 at 15:49 +0200, Arne Fitzenreiter wrote:
> Hi Micha, hi Dirk,
> 
> I think it is not a good idea to complete overwrite the logrotate.conf 
> at update because there are some
> user configurable settings inside. It is better to use sed for adding 
> the include line...
> 
> http://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=23b810171806939a23c3d5df7758b90dda357116
> 
> Arne
> 
> _______________________________________________
> Development mailing list
> Development(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/development


      reply	other threads:[~2014-07-10 15:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-10 13:49 Arne Fitzenreiter
2014-07-10 15:15 ` Michael Tremer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1405005340.16965.45.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox