Now, the skarnet rpm repo is hosted by GitHub Pages.
Please use the following command to verify it:
rpm --import https://ericwq.github.io/rpms/repo/RPM-GPG-KEY-wangqi
dnf config-manager --add-repo http://ericwq.github.io/rpms/repo/skarnet.repo
Currently, only support x86_64. Verified on
First, S6 rpm package is ready now. s6-svscan works as a systemd service
process.
The scan directory: /var/lib/s6/service, is monitored by rpm file triggers.
Logs is stored
in journald. s6-svscan is enabled after installation.
Second, for utmps rpm package, there are several options:
1. Run
At first, It’s my project depends on utmps service, I search the web and ask
the mail list, there
is no available rpm packages for utmps. I think I can build it and share it to
others. So I start this venture.
My initial goal is simple: get utmps works for my project and share it to the
Got your point, I will prepare a boot script for s6-svcan, prepare the scandir
in that script. Thanks.
Wang
> On Apr 10, 2024, at 15:36, Guillaume Perréal wrote:
>
> Well, I am not discussing whether using /run/service or not is the way to go.
> I am trying to point out that altering the
On alpine linux, s6 use /run/service as scandir.
On Redhat like linux distribution, we can discuss the best place for scandir.
> On Apr 10, 2024, at 13:14, Guillaume Perréal wrote:
>
> In some distributions, /run is a tmpfs so its content is lost on
> shutdown/reboot. If this is the case here,
About s6-svscanboot, I tried the following solution:
1. The only remain part is creating scandir (here is /run/service) at the
pre-install phase.
2. Don’t create ./.s6-svscan directory, according to s6 doc:
"If the ./.s6-svscan control directory does not exist, s6-svscan creates it. “
3. Don’t
Thanks for your reply. It helps me a lot. Hoël, I have the same thought as
yours, just need confirmation from upstream.
> On Apr 9, 2024, at 07:24, Laurent Bercot wrote:
>
> As Hoël said, it's a legacy script, for very old installations that need
> to upgrade. It could probably be removed. In
After check the installed package of execline on alpine. I choose to install
main part of execline to /usr/bin.
Create /usr/sbin directory, create relative symbol link for cd, umask and wait
to /usr/bin/execline.
# rebuild the conflicted files (filesystem, bash package) in /usr/sbin
mkdir -p
Two options:
1. Move the conflicted files: cd, umask and wait to /usr/sbin, while keep the
others in /bin directory.
2. Install all of them to /usr/sbin directory.
Which one is better?
Wang qi.
> On Apr 2, 2024, at 06:25, Laurent Bercot wrote:
>
> If the default PATH has /usr/sbin before
Yes, skalibs, execline are different projects. The GitHub site is just a
central and temporary place to hold the spec files.
For skalibs project, I build 4 rpm packages: skalibs, skalibs-devel,
skalibs-devel-static, skalibs-doc.
skalibs-devel depends on skalibs. Just follow the aports
Today, execline rpm package is ready now.
The following is the directory of rpmbuild.
[packager@rpm-builder rpmbuild]$ tree
.
├── BUILD
├── BUILDROOT
├── RPMS
│ └── x86_64
│ ├── execline-2.9.4.0-1.fc39.x86_64.rpm
│ ├── execline-devel-2.9.4.0-1.fc39.x86_64.rpm
│
ly one MIME part, specified by the "Content-Type" header as
>> "text/plain", even though it's obviously "text/html".
>>
>> "ericwq057" writes:
>>
>
15 matches
Mail list logo
