public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Stephen Ecker <stephenecker240@gmail.com>,
	isar-users <isar-users@googlegroups.com>
Subject: Re: dpkg-raw and debian/rules
Date: Fri, 10 Jan 2025 07:21:29 +0100	[thread overview]
Message-ID: <88f68457-7d94-4c29-83de-504390a2aec5@siemens.com> (raw)
In-Reply-To: <3fe52e49-8e23-4af6-b641-a6415547c8cbn@googlegroups.com>

On 10.01.25 04:35, Stephen Ecker wrote:
> I am trying to make a package using dpkg-raw, because I don't need to
> compile anything... but I would like to add a hook to the rules.  Is
> there a good way to do this, or will I need to provide the entire
> debian/ directory?

dpkg-raw used this:

https://github.com/ilbers/isar/blob/master/doc/user_manual.md#compilation-of-sources-missing-the-debian-directory
("Create rules file if sources does not contain a rules file")

What we are missing in our docs is a link from
https://github.com/ilbers/isar/blob/master/doc/user_manual.md#packages-without-source
to the debianize mechanism.

> 
> What I am actually trying to accomplish is a call to add with update-
> alternatives.  Is there a builtin way to do this already, by chance?

However, update-alternatives is a postinst topic, nothing for rules as
the latter runs during package build while you want something after
package installation.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/88f68457-7d94-4c29-83de-504390a2aec5%40siemens.com.

  reply	other threads:[~2025-01-10  6:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-10  3:35 Stephen Ecker
2025-01-10  6:21 ` 'Jan Kiszka' via isar-users [this message]
2025-01-10  6:47   ` Stephen Ecker
2025-01-10  7:26     ` Anton Mikanovich

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=88f68457-7d94-4c29-83de-504390a2aec5@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.com \
    --cc=stephenecker240@gmail.com \
    /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