Comments on: Work plan for M11 2019 http://thetarpit.org/2019/work-plan-vii "Now I feel like I know less about what that blog is about than I did before." Sun, 05 Apr 2026 17:15:22 +0000 http://thetarpit.org hourly 1 By: Work plan for (the rest of) M12 2019 « The Tar Pit http://thetarpit.org/2019/work-plan-vii#comment-419 Work plan for (the rest of) M12 2019 « The Tar Pit Wed, 14 Oct 2020 06:44:51 +0000 http://thetarpit.org/?p=338#comment-419 [...] Last month's (initial) plan got halted and then changed by the waves of the tumult spreading further, followed by a shift in perspective and immediate objectives within TMSR. In other words: that other work I was going to do was deemed "not that much of a priority", so the only major item1 in my M11 was the Cuntoo bootstrapper notepad -- not sure that's going anywhere either, since meanwhile TMSR-OS management changed and there seems to be an alternative out there, different in some respects, and currently in need of further examination2. [...] [...] Last month's (initial) plan got halted and then changed by the waves of the tumult spreading further, followed by a shift in perspective and immediate objectives within TMSR. In other words: that other work I was going to do was deemed "not that much of a priority", so the only major item1 in my M11 was the Cuntoo bootstrapper notepad -- not sure that's going anywhere either, since meanwhile TMSR-OS management changed and there seems to be an alternative out there, different in some respects, and currently in need of further examination2. [...]

]]> By: 2019 in review « The Tar Pit http://thetarpit.org/2019/work-plan-vii#comment-207 2019 in review « The Tar Pit Mon, 13 Jan 2020 16:54:09 +0000 http://thetarpit.org/?p=338#comment-207 [...] with it; and I made some minor modifications to ye olde Perl Vtron. Then as November began, stuff happened and... well, let's make a short parenthesis [...] [...] with it; and I made some minor modifications to ye olde Perl Vtron. Then as November began, stuff happened and... well, let's make a short parenthesis [...]

]]> By: spyked http://thetarpit.org/2019/work-plan-vii#comment-166 spyked Fri, 15 Nov 2019 12:24:31 +0000 http://thetarpit.org/?p=338#comment-166 An <b>update</b> on this month's schedule: following discussions in the forum (<a href="http://logs.ossasepia.com/log/trilema/2019-11-11#1950544" rel="nofollow">a</a>, <a href="http://logs.ossasepia.com/log/trilema/2019-11-12#1951030" rel="nofollow">b</a>, <a href="http://logs.ossasepia.com/log/trilema/2019-11-13#1951096" rel="nofollow">c</a>), I'm suspending bot works for the time being, in favour of Cuntoo work. For what remains of this week and at least the next one, I will be studying and running Trinque's <a href="http://trinque.org/2018/11/27/cuntoo-bootstrapper/" rel="nofollow">Cuntoo bootstrapper</a>, with a view towards understanding the way it works, its current limitations and what needs to be done in order to get to a proper TMSR OS. More on this soon. An update on this month's schedule: following discussions in the forum (a, b, c), I'm suspending bot works for the time being, in favour of Cuntoo work. For what remains of this week and at least the next one, I will be studying and running Trinque's Cuntoo bootstrapper, with a view towards understanding the way it works, its current limitations and what needs to be done in order to get to a proper TMSR OS. More on this soon.

]]> By: spyked http://thetarpit.org/2019/work-plan-vii#comment-151 spyked Wed, 06 Nov 2019 07:46:46 +0000 http://thetarpit.org/?p=338#comment-151 @<b>shinohai</b>: Figuring that out was the easiest thing. The confusing part came when for some reason pip couldn't access the repository, so I assumed that it went down (as they usually do, which is why I don't like relying on these arbitrary "repositories") and started searching for alternatives. To my surprise, the link was online, only the server now listens only on 443. @<b>Stanislav Datskovskiy</b>: I still think grabbing all the so-called libraries and adding them ad-litteram to the V tree is the right thing. While I agree that that'll result in a lot of bloat, it will to some degree that the thing will work on existing Unix+Python systems. @shinohai: Figuring that out was the easiest thing. The confusing part came when for some reason pip couldn't access the repository, so I assumed that it went down (as they usually do, which is why I don't like relying on these arbitrary "repositories") and started searching for alternatives. To my surprise, the link was online, only the server now listens only on 443.

@Stanislav Datskovskiy: I still think grabbing all the so-called libraries and adding them ad-litteram to the V tree is the right thing. While I agree that that'll result in a lot of bloat, it will to some degree that the thing will work on existing Unix+Python systems.

]]> By: Stanislav Datskovskiy http://thetarpit.org/2019/work-plan-vii#comment-150 Stanislav Datskovskiy Tue, 05 Nov 2019 17:13:25 +0000 http://thetarpit.org/?p=338#comment-150 Re 1: It's indeed a wartime kludge, and for the reasons others already described, i.e. demands quite heavy tower of ??? deps. Certainly wasn't written as a "logger for all time." Re 2: I will continue to log all chans that I find of interest, but only where the chan operator permits the bot to echo. (If anyone concretely does <b>not</b> want my bot in theirs, please let me know.) Re 1: It's indeed a wartime kludge, and for the reasons others already described, i.e. demands quite heavy tower of ??? deps. Certainly wasn't written as a "logger for all time."

Re 2: I will continue to log all chans that I find of interest, but only where the chan operator permits the bot to echo. (If anyone concretely does not want my bot in theirs, please let me know.)

]]> By: shinohai http://thetarpit.org/2019/work-plan-vii#comment-149 shinohai Tue, 05 Nov 2019 17:05:46 +0000 http://thetarpit.org/?p=338#comment-149 >there's a "pip" for every Python version and gotta choose the proper one. I loathe python myself but have found using `python -m pip install ` to save me a lot of headache, as it will explicitly use the python interpreter I have chosen using eselect, so I don't have to fuss about with remembering to use "pip" or "pip3.x" or whatever. >there's a "pip" for every Python version and gotta choose the proper one.

I loathe python myself but have found using `python -m pip install ` to save me a lot of headache, as it will explicitly use the python interpreter I have chosen using eselect, so I don't have to fuss about with remembering to use "pip" or "pip3.x" or whatever.

]]>