Skip to content

[Fix] bypass rpmbuild ln error - #210

Closed
canxin121 wants to merge 2 commits into
fastforgedev:mainfrom
canxin121:main
Closed

[Fix] bypass rpmbuild ln error#210
canxin121 wants to merge 2 commits into
fastforgedev:mainfrom
canxin121:main

Conversation

@canxin121

@canxin121 canxin121 commented Jul 31, 2024

Copy link
Copy Markdown

close #209
I bypassed this error by adding a new attribute 'bin_name' to specify the executable file name in the file path when creating the symbolic link.

'mkdir -p %{buildroot}%{_datadir}/pixmaps',
'cp -r %{name}/* %{buildroot}%{_datadir}/%{name}',
'ln -s %{_datadir}/%{name}/%{name} %{buildroot}%{_bindir}/%{name}',
'ln -s %{_datadir}/%{name}/${packageName ?? "%{name}"} %{buildroot}%{_bindir}/%{name}',

@MarkieMark MarkieMark Dec 9, 2024

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks as though this may no longer be sufficient in rpmbuild 4.20.0 (current F41) as the working directory during %install is no longer the flutter project (/dist/<versionBuild>/<projectName>-<versionBuild>-linux_rpm/rpmbuild/BUILD) (sub)directory; please see narrative at PR #236

@lijy91

lijy91 commented Jul 21, 2026

Copy link
Copy Markdown
Contributor

Thank you for the contribution. I am closing this PR because the executable-name problem is now handled by #313 through automatic BINARY_NAME detection, while custom package naming is handled by #355. Both are merged, and the related issue #209 is closed.

@lijy91 lijy91 closed this Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The generated RPM package does not install correctly

3 participants