From: reback00 <reback00@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: isoimagewriter-0.8
Date: Fri, 09 Oct 2020 07:28:15 +0200 [thread overview]
Message-ID: <20201009052815.hMIgvizny6lfR4yc9lJNwJuxniY0vfNHjOs_1l8FuBg@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-25417@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
New comment by reback00 on void-packages repository
https://github.com/void-linux/void-packages/pull/25417#issuecomment-705975965
Comment:
Manual.md says `$KDE_SITE="https://download.kde.org/stable"`, but the url starts with `https://download.kde.org/unstable/`. So can't be done. At least until it gets to `/stable` url.
> Can we wait until it enter stable?
Well, this package is fairly simple and it seems to be working fine. So I thought of creating this PR. Void had 0.9x.y version of Inkscape for a long time on the repo. It crashed at least 2 times a day when I used it, even with basic normal functions like creating shapes, ordering them, changing colors etc. I haven't used v1 of inkscape that much, but it crashed at least 1 time with light use. I have to save aggressively to get through the day. This package seems to be more stable than Inkscape. :) I've tested it ~15 times with ~5 iso images and they were all success. Althought it is KDE branded, any distro ISO can be written, Void included, with or without signature verification.
At the end of the day, it is up to you to decide, but having more packages in the repo is something nice. It is better than Etcher, at least, because it is native and does not rely on Electron. Tools like this are handy to have. I've heard that users complain Void having lack of packages. So I think this would be a nice addition.
prev parent reply other threads:[~2020-10-09 5:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-07 20:24 [PR PATCH] " reback00
2020-10-08 0:12 ` [PR PATCH] [Closed]: " sgn
2020-10-08 0:12 ` sgn
2020-10-09 5:28 ` reback00 [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201009052815.hMIgvizny6lfR4yc9lJNwJuxniY0vfNHjOs_1l8FuBg@z \
--to=reback00@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).