On 12/10/25 16:33, Rogier Wolff via Discuss wrote:
Worst case it's not directly evident that it's a BOSL2
regression and you spend time diagnosing a problem you
didn't cause...
I would argue this is not true. If you automate updates
and those updates break your stuff, it's your fault
unless you got a written guaranty from whatever that
dependency is.
A guaranty of that type usually costs quite a bit of
money.
ciao,
Torsten.
On Wed, Dec 10, 2025 at 04:51:10PM +0100, Torsten Paul via Discuss wrote:
On 12/10/25 16:33, Rogier Wolff via Discuss wrote:
Worst case it's not directly evident that it's a BOSL2
regression and you spend time diagnosing a problem you
didn't cause...
I would argue this is not true. If you automate updates
and those updates break your stuff, it's your fault
unless you got a written guaranty from whatever that
dependency is.
A guaranty of that type usually costs quite a bit of
money.
You're right. I worded it a bit wrong. I meant "... diagnosing a
problem that is not in the code you're working on".
I wanted to add, If you don't put in the auto-update, then you'll have
just typed "update bosl2" and it will be easier to find a problem that
the update caused.
Roger.
--
** R.E.Wolff@BitWizard.nl ** https://www.BitWizard.nl/ ** +31-15-2049110 **
** Verl. Spiegelmakerstraat 37 2645 LZ Delfgauw, The Netherlands.
** KVK: 27239233 **
f equals m times a. When your f is steady, and your m is going down
your a** is going up. -- Chris Hadfield about flying up the space shuttle.
** 'a' for accelleration.
On 12/10/2025 5:41 AM, larry via Discuss wrote:
Is there any downside to using a script running daily with cron, to
update BOSL2?
There's a small risk that it will update while you're in the middle of a
run. If you set the update for the middle of the night, that risk
should be very low... and the worst thing that should happen is that the
run fails.
On 12/10/2025 1:41 PM, Jordan Brown via Discuss wrote:
There's a small risk that it will update while you're in the middle of
a run. If you set the update for the middle of the night, that risk
should be very low... and the worst thing that should happen is that
the run fails.
Well, maybe also (depending on implementation) a small risk that the
update fails because it tries to delete or write a file that's in use.
Probably not an issue on UNIX-ish systems, might be an issue on Windows.
On Wed, 2025-12-10 at 16:51 +0100, Torsten Paul via Discuss wrote:
On 12/10/25 16:33, Rogier Wolff via Discuss wrote:
Worst case it's not directly evident that it's a BOSL2
regression and you spend time diagnosing a problem you
didn't cause...
I would argue this is not true. If you automate updates
and those updates break your stuff, it's your fault
unless you got a written guaranty from whatever that
dependency is.
I agree, and I am going to try to see if I can deal with that easily.
I think I'll try something like this...
Copy current BOSL2 to b2.old
cd to BOSL2
git pull >b2.txt ;result to b2.txt
edt b2.txt ;loads output into my text editor
Then if the update doesn't work, I can have a script that deletes the
new one and renames the old one.
Thanks to you, Rogier, and Adrian for the advice.
L
I can see how to run OpenSCAD from a command line with a specified script and send its rendered output to a specified file.
What I’d really like to do is something on the order of:
openscad -i foobar.stl -o foobar_modified.stl modify_input.scad
where ‘modify_input.scad’ is some variation of:
<do stuff to child> import(INPUTFILE);
where “INPUTFILE” is the “-i” parameter…which of course does not exist.
Any easy/clean way to do this?
Ah, never mind, I’m having a “senior moment”…completely misread the explanation of that “-D” argument.
From: Lee DeRaud via Discuss discuss@lists.openscad.org
Sent: Wednesday, December 10, 2025 4:41 PM
To: 'OpenSCAD general discussion Mailing-list' discuss@lists.openscad.org
Cc: lee.deraud@roadrunner.com
Subject: [OpenSCAD] Input parameters to OpenSCAD in CLI
I can see how to run OpenSCAD from a command line with a specified script and send its rendered output to a specified file.
What I’d really like to do is something on the order of:
openscad -i foobar.stl -o foobar_modified.stl modify_input.scad
where ‘modify_input.scad’ is some variation of:
<do stuff to child> import(INPUTFILE);
where “INPUTFILE” is the “-i” parameter…which of course does not exist.
Any easy/clean way to do this?
Oops, got a bit overconfident…
I’m using PowerShell on Windows and for the life of me, I cannot figure out the quoting/escapes
required to construct a command line when I’m passing in a string, specifically a filename.
Command line (typical; I’ve gotten different errors on other attempts):
PS A:\3D\Jaguar> openscad.com -D "IFILE=”"HoodBottom.stl"”" -o HoodBottom2.stl auto_hull.scad
Script (auto_hull.scad):
IFILE=”test.stl";
echo(IFILE);
hull() import(IFILE,center=false);
Result:
PS A:\3D\Jaguar> openscad.com -D "IFILE=""HoodBottom.stl""" -o HoodBottom2.stl auto_hull.scad
WARNING: Ignoring unknown variable "HoodBottom" in file auto_hull.scad, line 7
ECHO: undef
ERROR: Unsupported file format while trying to import file '""', import() at line 3
Current top level object is empty.
PS A:\3D\Jaguar>
Any help would be appreciated, because I am completely wrapped around the axle on this one.
From: Lee DeRaud via Discuss discuss@lists.openscad.org
Sent: Wednesday, December 10, 2025 4:50 PM
To: 'OpenSCAD general discussion Mailing-list' discuss@lists.openscad.org
Cc: lee.deraud@roadrunner.com
Subject: [OpenSCAD] Re: Input parameters to OpenSCAD in CLI
Ah, never mind, I’m having a “senior moment”…completely misread the explanation of that “-D” argument.
From: Lee DeRaud via Discuss <discuss@lists.openscad.org mailto:discuss@lists.openscad.org >
Sent: Wednesday, December 10, 2025 4:41 PM
To: 'OpenSCAD general discussion Mailing-list' <discuss@lists.openscad.org mailto:discuss@lists.openscad.org >
Cc: lee.deraud@roadrunner.com mailto:lee.deraud@roadrunner.com
Subject: [OpenSCAD] Input parameters to OpenSCAD in CLI
I can see how to run OpenSCAD from a command line with a specified script and send its rendered output to a specified file.
What I’d really like to do is something on the order of:
openscad -i foobar.stl -o foobar_modified.stl modify_input.scad
where ‘modify_input.scad’ is some variation of:
<do stuff to child> import(INPUTFILE);
where “INPUTFILE” is the “-i” parameter…which of course does not exist.
Any easy/clean way to do this?
Ask Copilot.
On Wed, Dec 10, 2025 at 10:12 PM Lee DeRaud via Discuss <
discuss@lists.openscad.org> wrote:
Oops, got a bit overconfident…
I’m using PowerShell on Windows and for the life of me, I cannot figure
out the quoting/escapes
required to construct a command line when I’m passing in a string,
specifically a filename.
Command line (typical; I’ve gotten different errors on other attempts):
PS A:\3D\Jaguar> openscad.com -D "IFILE=”"HoodBottom.stl"”"
-o HoodBottom2.stl auto_hull.scad
Script (auto_hull.scad):
IFILE=”test.stl";
echo(IFILE);
hull() import(IFILE,center=false);
Result:
PS A:\3D\Jaguar> openscad.com -D "IFILE=""HoodBottom.stl""" -o
HoodBottom2.stl auto_hull.scad
WARNING: Ignoring unknown variable "HoodBottom" in file auto_hull.scad,
line 7
ECHO: undef
ERROR: Unsupported file format while trying to import file '""', import()
at line 3
Current top level object is empty.
PS A:\3D\Jaguar>
Any help would be appreciated, because I am completely wrapped around the
axle on this one.
From: Lee DeRaud via Discuss discuss@lists.openscad.org
Sent: Wednesday, December 10, 2025 4:50 PM
To: 'OpenSCAD general discussion Mailing-list' <
discuss@lists.openscad.org>
Cc: lee.deraud@roadrunner.com
Subject: [OpenSCAD] Re: Input parameters to OpenSCAD in CLI
Ah, never mind, I’m having a “senior moment”…completely misread the
explanation of that “-D” argument.
From: Lee DeRaud via Discuss discuss@lists.openscad.org
Sent: Wednesday, December 10, 2025 4:41 PM
To: 'OpenSCAD general discussion Mailing-list' <
discuss@lists.openscad.org>
Cc: lee.deraud@roadrunner.com
Subject: [OpenSCAD] Input parameters to OpenSCAD in CLI
I can see how to run OpenSCAD from a command line with a specified script
and send its rendered output to a specified file.
What I’d really like to do is something on the order of:
openscad -i foobar.stl -o foobar_modified.stl
modify_input.scad
where ‘modify_input.scad’ is some variation of:
<do stuff to child> import(INPUTFILE);
where “INPUTFILE” is the “-i” parameter…which of course does not exist.
Any easy/clean way to do this?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
It may come to that. 😊At the moment Copilot is turned off on all of my machines, as was its predecessor, whose name I have purged from memory.
I was able to get it to work rather simply in CMD, but not in PowerShwll: I had not realized they use different escaping schemes.
Still can’t find a working combination in PS though.
From: Father Horton via Discuss discuss@lists.openscad.org
Sent: Wednesday, December 10, 2025 9:14 PM
To: OpenSCAD general discussion Mailing-list discuss@lists.openscad.org
Cc: Father Horton fatherhorton@gmail.com
Subject: [OpenSCAD] Re: Input parameters to OpenSCAD in CLI
Ask Copilot.
On Wed, Dec 10, 2025 at 10:12 PM Lee DeRaud via Discuss <discuss@lists.openscad.org mailto:discuss@lists.openscad.org > wrote:
Oops, got a bit overconfident…
I’m using PowerShell on Windows and for the life of me, I cannot figure out the quoting/escapes
required to construct a command line when I’m passing in a string, specifically a filename.
Command line (typical; I’ve gotten different errors on other attempts):
PS A:\3D\Jaguar> openscad.com <http://openscad.com> -D "IFILE=”"HoodBottom.stl"”" -o HoodBottom2.stl auto_hull.scad
Script (auto_hull.scad):
IFILE=”test.stl";
echo(IFILE);
hull() import(IFILE,center=false);
Result:
PS A:\3D\Jaguar> openscad.com http://openscad.com -D "IFILE=""HoodBottom.stl""" -o HoodBottom2.stl auto_hull.scad
WARNING: Ignoring unknown variable "HoodBottom" in file auto_hull.scad, line 7
ECHO: undef
ERROR: Unsupported file format while trying to import file '""', import() at line 3
Current top level object is empty.
PS A:\3D\Jaguar>
Any help would be appreciated, because I am completely wrapped around the axle on this one.
From: Lee DeRaud via Discuss <discuss@lists.openscad.org mailto:discuss@lists.openscad.org >
Sent: Wednesday, December 10, 2025 4:50 PM
To: 'OpenSCAD general discussion Mailing-list' <discuss@lists.openscad.org mailto:discuss@lists.openscad.org >
Cc: lee.deraud@roadrunner.com mailto:lee.deraud@roadrunner.com
Subject: [OpenSCAD] Re: Input parameters to OpenSCAD in CLI
Ah, never mind, I’m having a “senior moment”…completely misread the explanation of that “-D” argument.
From: Lee DeRaud via Discuss <discuss@lists.openscad.org mailto:discuss@lists.openscad.org >
Sent: Wednesday, December 10, 2025 4:41 PM
To: 'OpenSCAD general discussion Mailing-list' <discuss@lists.openscad.org mailto:discuss@lists.openscad.org >
Cc: lee.deraud@roadrunner.com mailto:lee.deraud@roadrunner.com
Subject: [OpenSCAD] Input parameters to OpenSCAD in CLI
I can see how to run OpenSCAD from a command line with a specified script and send its rendered output to a specified file.
What I’d really like to do is something on the order of:
openscad -i foobar.stl -o foobar_modified.stl modify_input.scad
where ‘modify_input.scad’ is some variation of:
<do stuff to child> import(INPUTFILE);
where “INPUTFILE” is the “-i” parameter…which of course does not exist.
Any easy/clean way to do this?
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org mailto:discuss-leave@lists.openscad.org