Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fedora Package #4

Open
bezborodow opened this issue Feb 24, 2024 · 13 comments
Open

Fedora Package #4

bezborodow opened this issue Feb 24, 2024 · 13 comments
Assignees

Comments

@bezborodow
Copy link
Member

bezborodow commented Feb 24, 2024

Packaging Tutorial:

  1. Fedora Accounts System

    1. Add SSH Key
  2. Installing Packager Tools.

    1. sudo dnf install fedora-packager fedora-review

    2. sudo usermod -a -G mock <your_local_username>

    3. Koji uses Kerberos for authentication.

      Acquire Kerberos ticket: fkinit -u <fedora-username>

      Say hello: koji moshimoshi

      Renew with: kinit -R

  3. Spec file: ee6d598

  4. Download source:

    spectool -g cidrl.spec (this is based on the Git tag in the version.)

  5. Build the package:
    fedpkg --release f38 mockbuild

@bezborodow bezborodow self-assigned this Feb 24, 2024
@bezborodow
Copy link
Member Author

It seems like I need to have a configure script.

./configure: No such file or directory

@bezborodow
Copy link
Member Author

@bezborodow
Copy link
Member Author

bezborodow commented Mar 25, 2024

sudo dnf install autoconf automake

@bezborodow
Copy link
Member Author

bezborodow commented Mar 25, 2024

Using autoscan to Create `configure.ac'

autoscan
# Manually check configure.scan. 
mv configure.scan configure.ac
autoreconf -i

bezborodow added a commit that referenced this issue Mar 25, 2024
configure: error: cannot find sources (cidrl.c cidrl6.c) in . or ..

— Macro: AC_CONFIG_SRCDIR (unique-file-in-source-dir)

unique-file-in-source-dir is some file that is in the package's source
directory; configure checks for this file's existence to make sure that
the directory that it is told contains the source code in fact does.
Occasionally people accidentally specify the wrong directory with
--srcdir; this is a safety check. See configure Invocation, for more
information.

https://www.gnu.org/software/autoconf/manual/autoconf-2.67/html_node/Input.html
@bezborodow
Copy link
Member Author

Now I am getting:

[dbezborodov@damo-hm0 cidrl]$ ./config.status 
config.status: error: cannot find input file: `Makefile.in'

bezborodow added a commit that referenced this issue Mar 25, 2024
@bezborodow
Copy link
Member Author

@bezborodow
Copy link
Member Author

@bezborodow
Copy link
Member Author

From fedpkg --release f38 mockbuild, got:

...
configure: error: cannot find required auxiliary files: compile missing install-sh
...
Could not execute mockbuild: Failed to execute command.

So, git add install-sh also.

bezborodow added a commit that referenced this issue Mar 25, 2024
Could not execute mockbuild: Failed to execute command.

due to:

configure: error: cannot find required auxiliary files: compile missing install-sh
@bezborodow
Copy link
Member Author

configure: error: cannot find required auxiliary files: compile missing

@bezborodow
Copy link
Member Author

bezborodow commented Mar 25, 2024

Hmmm, rabbit hole... https://stackoverflow.com/questions/3290908/which-files-generated-by-autotools-should-i-keep-in-version-control-repository

Maybe get Fedora packager to run autoreconf for me? Or do some sort of Git hook?

Can it be defined in the spec file to run autoreconf?

@bezborodow
Copy link
Member Author

@bezborodow
Copy link
Member Author

bezborodow commented Mar 25, 2024

It seems like Autoconf stuff should be in the archive. Since I am using GitHub to host release files based on tags, I might need to check the autoconf generated files into version control (something I wish to avoid.) Then... unless the packager can include it for me somehow (without building on the end users machine obviously) or if Github has a hook to include files into the release archive (unlikely?)

Or host my releases somewhere else?

bezborodow added a commit that referenced this issue Mar 25, 2024
@bezborodow
Copy link
Member Author

What on Earth?

configure: error: in `/builddir/build/BUILD/cidrl-1.0.0':
configure: error: C compiler cannot create executables

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant