c-std-porting.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely@redhat.com>
To: balaji marisetti <balajimarisetti@gmail.com>
Cc: c-std-porting@lists.linux.dev
Subject: Re: Help getting started with compiling rawhide sources
Date: Tue, 26 Dec 2023 19:20:00 +0000	[thread overview]
Message-ID: <CACb0b4kVtQPfCziiq=-RurU+QCZnYNwXngQ1JV_hOAr9KXF9SA@mail.gmail.com> (raw)
In-Reply-To: <CAKcrOwcazB8v+4AJykjiC6Qp-JkeB6Nn1dqZu5g2OCSYx52P2A@mail.gmail.com>

On Sat, 23 Dec 2023 at 08:59, balaji marisetti
<balajimarisetti@gmail.com> wrote:
>
> Hello,
>
> I'm new to Fedora development workflow. I want to help with porting a
> package or two as part of Fedora  Modern C initiative. I went through
> the link below, but it assumes some familiarity with Fedora tools and
> the development process, but I'm completely new to Fedora.
>  https://fedoraproject.org/wiki/Toolchain/PortingToModernC
>
> Can someone point me to a tutorial or a starting guide to Fedora
> development? I currently have a Fedora-39 running in a Virtualbox.
> Also I have the podman container with the instrumented gcc (mentioned
> in the link above) running inside the Fedora-39 instance.
>
> I cloned this repo https://src.fedoraproject.org/rpms/nbdkit, but I
> couldn't find any c-sources inside it. How to start building from this
> repo?

Since your question is about Fedora packaging, it would make more
sense to ask on a Fedora-specific mailing list.

This is the guide you're looking for:
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutorial_GNU_Hello/

Specifically, the "Installing Packager Tools" and "Building the
Package" sections.


      reply	other threads:[~2023-12-26 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-23  8:49 Help getting started with compiling rawhide sources balaji marisetti
2023-12-26 19:20 ` Jonathan Wakely [this message]

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='CACb0b4kVtQPfCziiq=-RurU+QCZnYNwXngQ1JV_hOAr9KXF9SA@mail.gmail.com' \
    --to=jwakely@redhat.com \
    --cc=balajimarisetti@gmail.com \
    --cc=c-std-porting@lists.linux.dev \
    /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 NNTP newsgroup(s).