Hello Debian developers and maintainers,
When I started to venture into building my own .deb packages, I
discovered that the process is (at least in my opinion) relatively
complex and arduous, and a variety of tools, sometimes overlapping,
exist to facilitate the process. On the other hand, Solus (another distribution with which I have been involved in terms of packaging)
has a highly streamlined packaging process where most steps are
automated and the only input required is the URL of the source
tarball, the name of the package, and the steps to install the
program, and a tool called solbuild (https://github.com/solus-project/solbuild) then uses OverlayFS to
make a container, download the tarball, run the installation steps,
detect which files were created by the installation script of the
software, and then build the package, all automatically without
requiring any sort of manual intervention. So I was thinking that
perhaps this approach might be applied to Debian to streamline the
packaging process and make it easier for people to contribute and
maintain packages. Do you think this would be a good idea? If so, I
would love to work on it (I am familiar with Go, Rust and Python).
Thank you,
Jeremy (jwinnie)
<div>Hello Debian developers and maintainers,<br></div><div><br></div><div>When I started to venture into building my own .deb packages, I discovered that the process is (at least in my opinion) relatively complex and arduous, and a variety of tools,sometimes overlapping, exist to facilitate the process. On the other hand, Solus (another distribution with which I have been involved in terms of packaging) has a highly streamlined packaging process where most steps are automated and the only input
<div><br></div><div>See: <a href="https://wiki.debian.org/sbuild">https://wiki.debian.org/sbuild</a> (I updated this recently for source only upload compatible shape)</div><div><br></div><div>sbuild default setting uses OverlayFS.</
<div><br></div><div>Osamu</div><div><br></div><div><br></div><div><br></div><div><span></span></div></body></html>
Hello Debian developers and maintainers,Solus (another distribution with which I have been involved in terms of packaging) has a highly streamlined packaging process where most steps are automated and the only input required is the URL of the source tarball, the name of the package, and the
When I started to venture into building my own .deb packages, I discovered that the process is (at least in my opinion) relatively complex and arduous, and a variety of tools, sometimes overlapping, exist to facilitate the process. On the other hand,
Thank you,
Jeremy (jwinnie)
Hello Jeremy,
I already try to do so.
I'm writing a shell script to automate the build process as far as possible.
And I'm documenting it literally.
I do it in German and it is prepared for translation.
Source: https://salsa.debian.org/ddp-team/dpb
Book: https://people.debian.org/~mechtilde/Dokumentatio
Cooperation is welcome.
HI,Yes, but I can't do it.
On Sun, 2021-04-18 at 07:56 +0200, Mechtilde wrote:
Hello Jeremy,
I already try to do so.
I'm writing a shell script to automate the build process as far as possible. >>
And I'm documenting it literally.
I do it in German and it is prepared for translation.
Source: https://salsa.debian.org/ddp-team/dpb
Book: https://people.debian.org/~mechtilde/Dokumentatio
Cooperation is welcome.
Looks interesting.
Have you thought about improving existing ones.
https://www.debian.org/doc/devel-manuals#debmake-doc
or even its previous version.
https://www.debian.org/doc/devel-manuals#maint-guide
They already come with translations.
Very verbose documentation doesn't help much since we are working on
the moving target.
Biggest shortcomings are:
They don't use the current sbuild.
They are not updated on time.
I think gbp will stay here but the use of dgit will increase. For the
chroot build system, there is not much reason not to use sbuild.
After all, it share the same build system as the official buildd.
It uses overlay mount and it is supported by kernel for good long time
and we can use any filesystem. (NO LVM or Btrfs required.) (Except "I
don't like Perl" like me. Well, I even had to work on uscan in Perl to
be useful to others.)
https://wiki.debian.org/sbuild
I will change https://www.debian.org/doc/devel-manuals#debmake-doc
to use sbuild after bullseye. https://salsa.debian.org/debian/debmake-doc/-/tree/sbuild
It is non-trivial to do piupitus and autopkgtest with
pbuilder/cowbuilder. gbp can be used with sbuild now.
apt-cache-ng has some issue for deb.debian.org in its chroot apt line
but I think that can be adddressed ...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986356
Regards,
Osamu
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 48:58:52 |
Calls: | 6,648 |
Files: | 12,200 |
Messages: | 5,330,096 |