github-starred/firejail

Fork 0

mirror of https://github.com/netblue30/firejail.git synced 2026-05-15 14:16:14 -06:00

[GH-ISSUE #437] Using mkdeb to build firejail #317

New issue

Closed

opened 2026-05-05 05:35:32 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 05:35:32 -06:00

Owner

Originally created by @Fred-Barclay on GitHub (Apr 14, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/437

G'day netblue30. This isn't an issue per se, at least not yet--I just need more info on building a firejail.deb package.

After downloading the source code and cd-ing into the directory, how do I build the .deb? Do I immediately run ./mkdeb.sh? Do I ./configure first? Are there any intermediate steps?

When installing the .deb, is it prefixed to /usr/local? I noticed that building from source does this, but I'd definitely not prefer this behavior if I dpkg -i firejail.deb. (In another words, does it build a .deb that behaves the same as one I download from your repo on SourceForge? Ignoring changes/updates, of course.)

Thanks!
Fred

Originally created by @Fred-Barclay on GitHub (Apr 14, 2016). Original GitHub issue: https://github.com/netblue30/firejail/issues/437 G'day netblue30. This isn't an issue per se, at least not yet--I just need more info on building a firejail.deb package. After downloading the source code and cd-ing into the directory, how do I build the .deb? Do I immediately run `./mkdeb.sh`? Do I `./configure` first? Are there any intermediate steps? When installing the .deb, is it prefixed to /usr/local? I noticed that building from source does this, but I'd definitely not prefer this behavior if I `dpkg -i firejail.deb`. (In another words, does it build a .deb that behaves the same as one I download from your repo on SourceForge? Ignoring changes/updates, of course.) Thanks! Fred

gitea-mirror

2026-05-05 05:35:32 -06:00

closed this issue
added the
information_old
label

gitea-mirror commented

2026-05-05 05:35:38 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 15, 2016):

First you configure it, than you do make deb:

$ ./configure
$ sudo make deb

The package is prefixed automatically to /usr.

@netblue30 commented on GitHub (Apr 15, 2016): First you configure it, than you do make deb: ``` $ ./configure $ sudo make deb ``` The package is prefixed automatically to /usr.

gitea-mirror commented

2026-05-05 05:35:40 -06:00

Author

Owner

@Fred-Barclay commented on GitHub (Apr 15, 2016):

Thanks, mate.
Would it be possible to avoid prefixing to /usr? Or is that a really bad idea?
(EDIT: Sorry, didn't mean to close it just yet.)

@Fred-Barclay commented on GitHub (Apr 15, 2016): Thanks, mate. Would it be possible to avoid prefixing to /usr? Or is that a really bad idea? (EDIT: Sorry, didn't mean to close it just yet.)

gitea-mirror commented

2026-05-05 05:35:40 -06:00

Author

Owner

@netblue30 commented on GitHub (Apr 16, 2016):

Usually packages you compile yourself end up in /usr/local/bin, and .deb or .rpm packages you download are placed under /usr/bin. These are old rules, you can get around them as you like, I don't think it matters.

You can modify mkdeb.sh:

$ cat mkdeb.sh
[...]
tar -xjvf $CODE_ARCHIVE
#mkdir -p $INSTALL_DIR
cd $CODE_DIR
./configure --prefix=/usr
make
mkdir debian
DESTDIR=debian make install-strip
[...]

You need to change "./configure --prefix=/usr" to "./configure".

@netblue30 commented on GitHub (Apr 16, 2016): Usually packages you compile yourself end up in /usr/local/bin, and .deb or .rpm packages you download are placed under /usr/bin. These are old rules, you can get around them as you like, I don't think it matters. You can modify mkdeb.sh: ``` $ cat mkdeb.sh [...] tar -xjvf $CODE_ARCHIVE #mkdir -p $INSTALL_DIR cd $CODE_DIR ./configure --prefix=/usr make mkdir debian DESTDIR=debian make install-strip [...] ``` You need to change "./configure --prefix=/usr" to "./configure".

gitea-mirror commented

2026-05-05 05:35:41 -06:00

Author

Owner

@Fred-Barclay commented on GitHub (Apr 16, 2016):

...which would explain why ./configure --prefix= seemed to have no effect on the .deb.
Thanks!

@Fred-Barclay commented on GitHub (Apr 16, 2016): ...which would explain why `./configure --prefix=` seemed to have no effect on the .deb. Thanks!

gitea-mirror referenced this issue

2026-05-05 10:04:18 -06:00

[PR #317] [MERGED] man/firejail.txt: note you don't need --ip6= with SLAAC #3595

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/firejail#317

No description provided.

Rows
Columns