Simple-shell | An attempt to create a simple command line shell | Interpreter library
kandi X-RAY | Simple-shell Summary
kandi X-RAY | Simple-shell Summary
e.g. support some UNIX commands, 'cd'ing directly to other drives(multiple root currently NOT supported), default loading functions in dlls (as void function()or as int function(int, char**)), default UTF-8 codepage (in the near future), etc...
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of Simple-shell
Simple-shell Key Features
Simple-shell Examples and Code Snippets
Community Discussions
Trending Discussions on Simple-shell
QUESTION
I'm trying to test Wazuh configuration related to half-configured packages. So, I'm trying to create a .deb
package that will end up half configured when installed.
I started by following these instructions for creating a dirt-simple, do-nothing package.
I tried changing the exit code of debian/postinst.ex
to 1, but the package installed successfully anyway.
I tried adding a non-existing file to debian/conffiles
, but debuild
failed.
I've also searched all over for information on the things that can cause a package to be left half configured, without any luck.
Thanks!
...ANSWER
Answered 2021-Mar-24 at 10:03First of all, I want to mention that there are two different status for failed installed packages:
- half-configured: The package is unpacked and configuration has been started, but not yet completed for some reason.
- half-installed: The installation of the package has been started, but not completed for some reason.
Source: https://www.man7.org/linux/man-pages/man1/dpkg.1.html
If you want a half-configured package, then the package must be unpackaged and it is the configuration step the one that should fail.
Now, if you follow the guide you shared with us, you may have missed the part where it says that the *.ex
files are examples and are not introduced in the package so if you're modifying the file postinst.ex
, these changes will no take effect.
You can remove all the *.ex
files and create your own postinst
file. For example I've used this one:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install Simple-shell
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page