<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
I don't like the idea of having multiple packages.<br> And I don't see that it helps -- I don't know why installing the current .deb files doesn't work, fairly independent of what is installed (assuming there is at least gcc/ld/libc).<br><br><br>I want there to be close to one download per-target, and I want the web pages to sniff from the agent string which download to steer the user to, like the Firefox download pages do, with a link to a list of everything so user can chose, e.g. if they are downloading to run on other than the current system.<br>(one .deb or .msi or .dmg, etc., one .tar.gz/bz2/xz/lzma)<br><br><br>I find the current proliferation of packages, that we already have, confusing.<br>I'm ok with their being a separate set for "minimal to bootstrap from source".<br><br><br>I understand that things are in fact modular. That there is in fact a dependency tree. And it isn't very complicated. The system isn't monolithic.<br>But I don't think presenting users with many choices is friendly.<br><br><br>I understand that the world -- really, the larger world, beyond computers -- is modular. As is the computer world.<br>Parts come and go (people, buildings, roads, cars, etc.).<br>But considering things as being composed of too many too small pieces (atoms, molecules) gets confusing.<br><br><br>Maybe my tendency is toward too few too large pieces.<br><br><br> - Jay<br><br><div>> Date: Wed, 15 Jun 2011 17:39:33 -0400<br>> From: hendrik@topoi.pooq.com<br>> To: m3devel@elegosoft.com<br>> Subject: Re: [M3devel] helo everyone - videotutorials for modula3<br>> <br>> On Wed, Jun 15, 2011 at 02:49:26PM -0500, felipe valdez wrote:<br>> > hello everyone.<br>> > <br>> > this is me just nagging, and complaining, but not actually doing any useful<br>> > work,<br>> > but, I guess a logic along the lines of:<br>> > <br>> > do you want postgress integration (optional)?<br>> > >no<br>> > if( YES )<br>> > please provide the path<br>> > else<br>> > you have chosen not to integrate at this point.<br>> > if you ever need to in the future, follow these instructions,<br>> > http://example.com/instructions<br>> > end if<br>> > <br>> > instead of:<br>> > <br>> > do you have the exact path of the non-optional-but-required component?<br>> > >nope<br>> > ok, then, I'll stop working, until you install the non-required dependency.<br>> <br>> The usual way this stuff is done in Debian is to have the connection <br>> with postgress be a separate packate, called something like <br>> modula3-postgress. and whose description would say "postress binding for <br>> modula3.<br>> <br>> The postinstall scripts for modula3 and mosula3-postgress would <br>> each check for the other package and make the necessary adjustments.<br>> <br>> modula3-postgress would depend both on modula3 and on postgress.<br>> <br>> There are probably a few library bindings for which this treatment would <br>> be appropriate.<br>> <br>> -- hendrik<br></div> </div></body>
</html>