[arch-dev-public] Questions about Archlinux branding/artwork for KDE

Thayer Williams thayer at archlinux.org
Fri May 30 10:55:20 EDT 2008


On Fri, May 30, 2008 at 7:48 AM, Thayer Williams <thayer at archlinux.org> wrote:
> So long as *someone* is willing to maintain the the rc.d scripts, I'm
> fine with keeping them around. Personally, I have always used the
> inittab method--I think it _is_ documented somewhere as The Best Way
> To Do Things =)
>
> If we ever reach a point where devs don't want to maintain this kind
> of fluff, we could look at the deprecating the scripts as mentioned.
>
>
> On Fri, May 30, 2008 at 7:37 AM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
>> On Fri, May 30, 2008 at 5:57 AM, Xavier <shiningxc at gmail.com> wrote:
>>> On Thu, May 29, 2008 at 6:24 PM, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
>>>> On Wed, May 28, 2008 at 6:57 PM, Pierre Schmitz <pierre at archlinux.de> wrote:
>>>>> One should start kdm via inittab.
>>>>
>>>> I agree with Pierre, except for the rc.d script point - too many
>>>> people use it, and all the other login managers have rc.d scripts to.
>>>>
>>>>
>>>
>>> Isn't there a little problem here?
>>> People should use inittab, yet many people use rc.d scripts.
>>> It is probably not a big deal since I guess both methods usually work
>>> fine, but maybe it should be somehow made clearer that inittab is the
>>> preferred way.
>>> For example by deprecating the rc.d scripts and planning a future
>>> removal instead of removing them now.
>>
>> Who said people should use inittab? Is this documented somewhere as
>> The Only Way To Ever Do Things? I use the slim rc.d script and have
>> for ages. I don't see anything wrong with providing choice.
>>
>>
>

Ugh! Sorry for top posting before...my greasemonkey scripts are down
at the moment.

Does anyone mind if I update the kde-common i686 package to remove the
artwork stuff?  I see Tobias is the maintainer, but he's currently
away right?

I'll be out for the morning, but I'd like to get this wrapped up when
I get back.




More information about the arch-dev-public mailing list