Ah, I forgot the fourth point: I had fun writing it.
Don't forget that the "I had an idea for a fun toy project" is what
starts/drives most of our OSS ecosystem, including the start of Linux
itself :)
- René
Am 16.07.23 um 20:41 schrieb René Neumann:
Am 16.07.23 um 18:14 s
Am 16.07.23 um 18:14 schrieb Polarian:
You can simply use git clone to clone the repository from the dumb http
frontend, and then use git log to show the logs, I do not see why this
needs to be wrapped with a script as it is already a simple process to do.
First: I'd need the repo URL for clon
Hey everyone,
I noted that, from time to time, I want to determine the latest upstream
changes in a PKGBUILD, especially when only the pkgrel has changed (i.e.
not just a version bump).
As it involved remembering the web interfaces and hunt down the package
in question, I got tired of it and
To generate the list, I'd propose:
pacman -Qeq > list.txt
-e : only explicitly installed packages (deps get installed anyways...)
-q : output better suited for scripts
And on the other machine, just do the obvious:
pacman -S - < list.txt
(Note the single '-', specifiying to read the list of
Hi Andy,
not a solution, but a hint to gather further infos:
- use `xprop` to find infos about the window in question. Among other
things, this gives you a PID
- with `cat /proc/$PID/cmdline` you can see how it was spawned (other
files in /proc/$PID/ might give other interesting infos).
HTH,
Am 16.01.21 um 19:05 schrieb u34--- via arch-general:
$ drill -S .
;; Number of trusted keys: 2
;; Chasing: . A
drill: ./rdata.c:33: ldns_rdf_get_type: Assertion `rd != NULL' failed.
zsh: abort (core dumped) drill -S .
Is core dumping arch specific?
The above is with ld
