Github messages for voidlinux
 help / color / mirror / Atom feed
From: shahab-vahedi <shahab-vahedi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Add Printer Support: Brother DCP-L8410CDW
Date: Thu, 24 Oct 2024 21:34:44 +0200	[thread overview]
Message-ID: <20241024193444.DD2C82F7D1@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51608@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 2348 bytes --]

New comment by shahab-vahedi on void-packages repository

https://github.com/void-linux/void-packages/pull/51608#issuecomment-2436193837

Comment:
> I'm not inclined to accept these packages. At best, this ought to be considered for inclusion as a restricted package

I can add `restricted=yes` to the `template`. HOWEVER, if the community doesn't want this package, then I keep it to myself. I just wanted to share it with other Void users to save them some time.

> The EULAs and wrapper script should not be vendored...
For the EULA, my point of reference was the [agree.html](https://github.com/void-linux/void-packages/commits/master/srcpkgs/brother-brscan4/files/agree.html) already existing in `bother-brscan4` package.

Regarding the _wrapper script_, If you're referring to `cupswrapperdcpl8410cdw.void`, it's a trimmed down version of the original script in the `*.deb` file to suit a Void Linux system. The alternative would be to have the original one installed and apply a _patch_ on top of it. For ease of maintenance, I chose the former approach. For the record, the [brother-dcp197c-cupswarpper](https://github.com/void-linux/void-packages/blob/master/srcpkgs/brother-dcp197c-cupswrapper/files/cupswrapper.void), as it is in `master` branch of 24-Oct-2024, was my inspiration.

> ...Fetch them from the deb archive or the web at build time.

I find nothing in the `*.deb` file. As for the _web_, I neither am sure where that would be nor have I the will to locate it. Maybe I should just remove the `agree.html`.

> The INSTALL and REMOVE scripts are inappropriate and should be removed.
> Our packages don't restart users' services just by virtue of installation or removal.
> Users can restart their own services when appropriate.

This was a mimic of the `*.deb` package itself, but sure, I can remove them. Keep in mind, one of them, `brother-dcp8410-lpr/INSTALL`, is creating a directory and has nothing to do with the services.

I appreciate that someone has finally taken a peek at this. Whatever the outcome of this discussion will be, it will inherently be the same for my other [PR](https://github.com/void-linux/void-packages/pull/51636) which upgrades (and fixes) the (broken) existing package of [brother-brscan4](https://github.com/void-linux/void-packages/commits/master/srcpkgs/brother-brscan4/).

  parent reply	other threads:[~2024-10-24 19:34 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 14:58 [PR PATCH] " shahab-vahedi
2024-08-02 16:37 ` [PR PATCH] [Updated] " shahab-vahedi
2024-08-04 22:04 ` shahab-vahedi
2024-08-05  7:39 ` shahab-vahedi
2024-08-05  7:53 ` shahab-vahedi
2024-08-05  7:56 ` shahab-vahedi
2024-08-10 19:57 ` shahab-vahedi
2024-08-17  6:39 ` shahab-vahedi
2024-08-25 13:39 ` shahab-vahedi
2024-08-31 17:56 ` shahab-vahedi
2024-09-09  7:41 ` shahab-vahedi
2024-10-24 19:34 ` shahab-vahedi [this message]
2024-10-24 19:35 ` shahab-vahedi
2024-10-25 13:26 ` ahesford
2024-10-25 17:29 ` shahab-vahedi
2024-10-28 18:49 ` shahab-vahedi
2024-10-28 20:52 ` [PR PATCH] [Updated] " shahab-vahedi
2024-10-28 20:58 ` shahab-vahedi
2024-10-29 12:59 ` ahesford
2025-01-28  1:57 ` github-actions
2025-02-11  1:58 ` [PR PATCH] [Closed]: " github-actions

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=20241024193444.DD2C82F7D1@inbox.vuxu.org \
    --to=shahab-vahedi@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).