- This topic has 19 replies, 6 voices, and was last updated Jan 31-12:16 pm by anticapitalista.
-
Posts
-
Anonymous
[ -e "$WORKING_DIR" ]mktemp -d
(a manpage is available for the mktemp command)
https://ostechnix.com/the-mktemp-command-tutorial-with-examples-for-beginners/Robin
Hi skidoo,
you are right, I just managed to transfer the merge request. This gitlab page is a nightmare. You can’t find the fundamental functions well-aranged, but have to guess where and what instead. The places seem And the manual presents screenshots which show things in completely different places. Who could guess they differenciate between clone and fork. First I created a clone, simply because there was apparently no other button to create something like a fork, so I presumed it was a slightly divergent translation only. This was the reason I could not chose anticapitalista as target. But now, trying to correct this was even worse. They wouldn’t let me fork, since they told me the path was in use already. No explanation why, I could only guess they meant the other clone. Actually I had to delete all the correction work I had done in git already, and start from scratch with forking. After I had successfully created the first merge request, they wouldn’t let me do the second one. Nowhere was clearly visible, they had put silently the second one into the first already. In my eyes this page is pure chaos, but I’m sure this is only since I’m not a real programmer. I’m obviously trained in a completely different way of structured thinking, so I’ll probably be lost completely on this gitlab page forever. Never seen a confusion like that.Well, finally I’ve managed it. That’s what counts. I really hope I didn’t produce some unintended flaws into the requests, while struggling with tons of check-boxes and options on the way through, some of which I didn’t even understand the meaning… Please examine carefully whether the script code I intended to upload hasn’t suffered from all this fuss. Really, this page distracts me from the gist of the task.
P.S. Not to forget: Thank you very much for helping me out.
- This reply was modified 2 years, 3 months ago by Robin.
Windows is like a submarine. Open a window and serious problems will start.
a manpage is available for the mktemp command
man mktempin terminal window should do it, I think? I came across this some time ago, but found in an antiX script (don’t remember which one it was) a bifurcation, which tests whether mktemp has succesfully created the temp file. If not, another way of creating the temp file was engaged. So I concluded, this mktemp technique might not be too reliable. May be this was misleading, but what else should this reduplication have been good for?Windows is like a submarine. Open a window and serious problems will start.
> the path was in use already. No explanation why
When the operation was requested, the path (sic) “gitlab.com/myusername/screenshot-antix” already existed. I agree that those terse error texts are confusing.
.
> what else should this reduplication have been good for?Someone may have used code from, copied code from, a script which existed prior to mktemp being widely available across distributions… or the behavior of the version of mktemp available at that time was different, or was undesirable?
https://sources.debian.org/src/coreutils/8.32-4/debian/changelog/
coreutils (8.28-1) unstable; urgency=low
[..]
* Get rid of old transition packages & logic for mktemp, timeout, and realpath
[..]
— > Mon, 02 Oct 2017
[..]
* coreutils now includes mktemp, but it is not included in this package
because debian already has a mktemp package with similar syntax.
[..]
— > Fri, 30 Nov 2007
anticapitalista
bugfix deb sent to repos – thanks Robin!
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
- You must be logged in to reply to this topic.
