1 |
On Wed, Mar 21, 2012 at 10:29 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> On Wed, 21 Mar 2012 00:40:27 -0400 |
3 |
> "Walter Dnes" <waltdnes@××××××××.org> wrote: |
4 |
> |
5 |
>> On Tue, Mar 20, 2012 at 01:18:24AM +0200, Alan McKinnon wrote |
6 |
>> |
7 |
>> > I'm not sure where you're going with this. We're discussing an init |
8 |
>> > system and good, simple ways to start services. App maintainers are |
9 |
>> > going to continue to do whatever they feel they ought to do, some |
10 |
>> > might write the systemd files, some might not - that is what already |
11 |
>> > happens. Someone has to write it and what goes in it depends on what |
12 |
>> > the app code does, not the other way round. |
13 |
>> |
14 |
>> The point I'm making is that if the initialization is moved into the |
15 |
>> binary, then the binary will have to be patched/modified/whatever. |
16 |
>> There's already somebody with a systemd overlay. Assuming that the |
17 |
>> initialization code gets shoved into the binary, how does it |
18 |
>> simultaneously support openrc/systemd/linux/bsd/Sun/HPUX/etc/etc? The |
19 |
>> only realistic answer I see is leaving the init code to the distro |
20 |
>> maintainer. We don't expect the upstream for sshd or any other |
21 |
>> software to write Gentoo-specific stuff like ebuilds. Whey should |
22 |
>> they be expected to write Gentoo-specific initscripts? |
23 |
> |
24 |
> Fair enough |
25 |
> |
26 |
>> > As for the last question, I really have no idea where you're taking |
27 |
>> > this. I don't know the answer, I've never been a maintainer in that |
28 |
>> > position. Being the arrogant shit that I am, I reckon I would |
29 |
>> > probably tell the user to piss off and I don't support hobby crap. |
30 |
>> > But hey, that's just what I think I might say while sitting here on |
31 |
>> > my couch. |
32 |
>> |
33 |
>> So you're saying you wouldn't have supported... |
34 |
> |
35 |
> No, you're saying that you believe that you think I would say that |
36 |
> based on some extrapolation of I don't know what. |
37 |
> |
38 |
> I said no such thing. |
39 |
> I said that I don't know what I would do |
40 |
> |
41 |
> Let's not get too carried away with Linus's little project being |
42 |
> representative of anything. It's a fluke. There are 100s of other hobby |
43 |
> systems that went nowhere. |
44 |
|
45 |
I said this before, but it sounds useful to try to reiterate: |
46 |
|
47 |
* It's probable that service-specific files should not be included in |
48 |
the init system package. |
49 |
* Service-specific init files should probably be part of the |
50 |
distro-localized version of a service-providing package. |
51 |
|
52 |
This doesn't mean modifying binaries, this is part of bootstrapping a |
53 |
service's environment. Call it "deferred installation stages", if you |
54 |
like; things which need to be done for the service to be configured |
55 |
and properly operate. |
56 |
|
57 |
|
58 |
|
59 |
-- |
60 |
:wq |