Date: Sat, 16 Feb 2002 12:02:14 -0500 From: Ken Stailey <kstailey@surfbest.net> To: Alan Eldridge <alane@geeksrus.net> Cc: "."@babolo.ru, ports@FreeBSD.ORG, klh@panix.com Subject: Re: [ade@FreeBSD.org: suggests installing in a USER's HOME dir] Message-ID: <3C6E9096.3020708@surfbest.net> References: <20020216034549.GA51544@wwweasel.geeksrus.net> <200202160623.JAA27217@aaz.links.ru> <20020216070656.GA87963@wwweasel.geeksrus.net> <3C6E644B.3080102@surfbest.net> <20020216165229.GA33399@wwweasel.geeksrus.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alan Eldridge wrote:
>On Sat, Feb 16, 2002 at 08:53:15AM -0500, Ken Stailey wrote:
>
>>Alan Eldridge wrote:
>>
>>>On Sat, Feb 16, 2002 at 09:23:57AM +0300, "."@babolo.ru wrote:
>>>
>>>>Alan Eldridge writes:
>>>>
>>>>>----- Forwarded message from Ade Lovett <ade@FreeBSD.org> -----
>>>>>On 02/15/02 21:21, "Alan Eldridge" <alane@geeksrus.net> wrote:
>>>>>
>>>>>>But nobody ever did chime in with an idea of where the best place to put
>>>>>>a 200-400MB *writable* file, installed by a port, is. And that, of
>>>>>>course,
>>>>>>was the whole point in cc'ing portmgr. So, any thoughts on that?
>>>>>>
>>>>>Bottom line is, there's just no reliable way to pick a place that will
>>>>>fit
>>>>>the requirements of (1) unique to local machine (2) big enough (3)
>>>>>writable.
>>>>>
>>>>I think use of environment variable is good enough.
>>>>${EMULATOR_SPACE} for example (directory for all emulator's disk images)
>>>>administrator can set it in login.conf for everybody
>>>>or for some classes of users, user can set EMULATOR_SPACE for
>>>>himself, and no user install if script does not detect
>>>>this variable.
>>>>
>>>Ken, does it get directories from env as well as .ini file?
>>>
>>>If it doesn't, then this would entail some invasive software mods that
>>>I think are beyond the scope of a port, unless the original author was
>>>willing to incoroporate them into the base distribution.
>>>
>>I don't get this at all. Are you saying that it's OK to tell a user to
>>modify an env var but not an .ini file?
>>
>
>No, I suggesting that the above suggestion (using an env var) wouldn't
>be workable unless the code already supported it.
>
>I interpreted that suggestion as meaning an env var at RUN time, not
>port install time.
>
>Why don't you PR the beast(s) as you outlined it (below, elided)? Make
>sure the usr has to set a value for IMAGE_HOME. If it isn't set, fail the
>port make/install.
>
Sounds good to me. I'll PR it as soon as I make it really do what I
said and feel comfortable with it.
I threw together another doc:
Year 18-bitters 12-bitters 16-bitters 36-bitters
1960 PDP-1 --------------------------------------------------------
1961 | \
1962 PDP-4 <--- LINC -------- \
1963 | PDP-5 \ \ |
1964 PDP-7 | \ \ PDP-6
1965 | PDP-8 --\ | \ |
1966 | PDP-8/S LINC-8 | |
1967 | | | | KA10
1968 PDP-9 PDP-8/I,L | | |
1969 | | PDP-12 | |
1970 PDP-15 | PDP-14 PDP-11(/20) |
1971 | PDP-8/E / | \ |
1972 PDP-15/76 PDP-8/M - PDP-11/05 | PDP-11/45 -- KI10
1973 | / | PDP-11/40 | \ |
1974 | / | | | \ |
1975 PDP-8/A PDP-11/03 PDP-11/04 | | PDP-11/70 KL10
1976 | PDP-11/34 | PDP-11/55 | |
1977 VT78 | PDP-11/60 | |
1978 PDP-11/34C VAX-11/780 KS10
The first DEC 36-bit system, the PDP-6, came out in 1964. The PDP-10
line consisted of the KA which arrived in 1967, the KI in 1972. The
KL came out early in 1974; the KS was a 1978 entry. In 1984 the
unreleased KC was canceled.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C6E9096.3020708>