Mailinglist Archive: opensuse-factory (757 mails)
| < Previous | Next > |
Re: [opensuse-factory] Package Management Design and Experience
- From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@xxxxxxx>
- Date: Tue, 30 May 2006 16:26:35 +0200
- Message-id: <447C561B.9000601@xxxxxxx>
Andreas Hanke wrote:
> Volker Kuhlmann schrieb:
>> This thread is about what's annoying about the package management. .exe
>> processes are.
>
> .exe processes are neither specific to the package management nor can
> they be influenced by the people who are designing the package
> management architecture for SUSE Linux.
So you say that the SUSE package management designers were forced
to use mono .exe files regardless of whether it makes sense?
Interesting conspiracy theory.
> Try a Mono or, maybe even better, an ECMA mailing list.
Sorry, I googled for "ecma mailing list exe" and found nothing
relevant. However, some sites seem to suggest .exe is not the
only recommended suffix for .NET code.
>> The .exe extension is specific to the mswindows platform
>> (can one say of legendary notoriety?).
>
> No it isn't.
Examples please? (Except mono, which seems to be a reimplementation
of windows-only .NET code. And no, being able to use wine for some
.exe files doesn't make them cross-platform either.)
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
> Volker Kuhlmann schrieb:
>> This thread is about what's annoying about the package management. .exe
>> processes are.
>
> .exe processes are neither specific to the package management nor can
> they be influenced by the people who are designing the package
> management architecture for SUSE Linux.
So you say that the SUSE package management designers were forced
to use mono .exe files regardless of whether it makes sense?
Interesting conspiracy theory.
> Try a Mono or, maybe even better, an ECMA mailing list.
Sorry, I googled for "ecma mailing list exe" and found nothing
relevant. However, some sites seem to suggest .exe is not the
only recommended suffix for .NET code.
>> The .exe extension is specific to the mswindows platform
>> (can one say of legendary notoriety?).
>
> No it isn't.
Examples please? (Except mono, which seems to be a reimplementation
of windows-only .NET code. And no, being able to use wine for some
.exe files doesn't make them cross-platform either.)
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
| < Previous | Next > |