From: Catonano <catonano@gmail.com>
To: Aniket Patil <aniket112.patil@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Help with .deb, .rpm and guix packaging.
Date: Fri, 30 Oct 2020 08:03:42 +0100 [thread overview]
Message-ID: <CAJ98PDz6V6QAtuEU7d-0C2gj4YkmfCVG0Q4C4kTt89djeQtg=g@mail.gmail.com> (raw)
In-Reply-To: <CAF-xJgvWCRqXhv8hXhm4C5uJL+bUi1pVMYbvyCX1byNV9F5PPg@mail.gmail.com>
Hi Aniket,
Il giorno gio 29 ott 2020 alle ore 17:35 Aniket Patil <
aniket112.patil@gmail.com> ha scritto:
> 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?
>
>
Ehm, I think you're not right, no
Software packages don't need to be expressed as files (.deb, .tar, .rmp or
any other format)
That's a convention, not a necessity
mainstream Linux distributions adopt such a convention
Others do not
As an analogy, If you say that packages are .deb files, it's as if you're
saying that a document is the paper it's printed on
So what would be the relationship between a file representing such document
and the papers that can be printed by it ?
Some will say that the hand signed paper is "the document"
Others will say that the LibreOffice file is the document
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,
Guix doesn't release .deb or .rpm files for packages, no
but that's not "bypassing"
As long as distributing the file for a document is not bypassing the
distribution of printed copies
> 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?
>
Guix is ensuring that that the binary bits belonging to a package (produced
by compilig its source code) it runs are the same on everymachine that
built
the source with the same Guix recipe
And that's as an explicit producton of packages as I can think of
The idea that if there are no .deb files than the process is not explicit
is, in my opinion, not correct
> 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
>
The manual doesn't mention files and file formats because it doesn't assume
that software packages and files are identified
Binary files are a support, as paper id for documents
But the packages exist independently of supports (as documents do)
Hope this helps
next prev parent reply other threads:[~2020-10-30 7:04 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
2020-10-30 7:03 ` Catonano [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ98PDz6V6QAtuEU7d-0C2gj4YkmfCVG0Q4C4kTt89djeQtg=g@mail.gmail.com' \
--to=catonano@gmail.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.