From: Ekaitz Zarraga <ekaitz@elenq.tech>
To: Aniket Patil <aniket112.patil@gmail.com>
Cc: "help-guix@gnu.org" <help-guix@gnu.org>
Subject: Re: Help with .deb, .rpm and guix packaging.
Date: Thu, 29 Oct 2020 17:07:45 +0000 [thread overview]
Message-ID: <6wgbiRLB60D9cv_dHnrZMj-sgjYiSJ7k6JgnxcPY81yIMINq42Vm0uDXCyae2D89qzXihvg_Ey6WTloO_NMwlwxSkvsI1cndi9r2eK9yu9E=@elenq.tech> (raw)
In-Reply-To: <CAF-xJgvWCRqXhv8hXhm4C5uJL+bUi1pVMYbvyCX1byNV9F5PPg@mail.gmail.com>
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, October 29, 2020 5:34 PM, Aniket Patil <aniket112.patil@gmail.com> wrote:
> Hi,
> There are GNU/Linux distros which are Debian-based or fedora(Redhat) based
> etc. What I know to my knowledge is GNU packages are .tar packages with
> .deb and .rpm file format, am I right? What I am wondering about how guix
> makes it happen? I mean are we bypassing the process of making the package
> in .deb and .rpm format and releasing it, or what exactly are we doing? To
> my knowledge, we are building from source code as we can see in the recipe.
> So that means we are bypassing the process of making packages explicitly
> for the distro, aren't we?
>
> Where can I learn more about this? I am going through guix manual but I
> don't know which chapter to look for. Also, where can I learn more about
> packaging software on GNU/Linux distribution? Like .deb or .rpm
>
> Regards,
> Aniket.
Hi Aniket,
In the distros you mention, software is pre-compiled and the .tar packages
have a directory structure that defines where do the packaged files need
to be installed. Those packages don't define how the software has to be
compiled and they don't include the sources.
Guix is not bypassing those systems: Guix is one of those systems. Guix is
a package manager.
The main difference is that Guix describes how is the source compiled and
installed in a recipe. When the user installs a package using:
guix install packagename
The package sources are downloaded, compiled and installed in the system,
following the recipe.
Guix also has ways to keep packages separated to avoid dependency collisions,
ad-hoc environments, time traveling, package installation history with a
reasonable rollback system... and some other interesting features.
Guix is also a software distribution built on top of the Guix package manager
that extends those interesting tools further and defines a uniform way to
describe your operating system.
Hope this helps.
If you have further questions, don't hesitate to ask them.
Regards,
Ekaitz
next prev parent reply other threads:[~2020-10-29 17:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 16:34 Help with .deb, .rpm and guix packaging Aniket Patil
2020-10-29 17:07 ` Ekaitz Zarraga [this message]
2020-10-30 7:03 ` Catonano
2020-10-30 12:10 ` Julien Lepiller
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='6wgbiRLB60D9cv_dHnrZMj-sgjYiSJ7k6JgnxcPY81yIMINq42Vm0uDXCyae2D89qzXihvg_Ey6WTloO_NMwlwxSkvsI1cndi9r2eK9yu9E=@elenq.tech' \
--to=ekaitz@elenq.tech \
--cc=aniket112.patil@gmail.com \
--cc=help-guix@gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).