search

fanglingsu / vimb

Vimb - the vim like browser is a webkit based web browser that behaves like the vimperator plugin for the firefox and usage paradigms from the great editor vim. The goal of vimb is to build a completely keyboard-driven, efficient and pleasurable browsing-experience.
https://fanglingsu.github.io/vimb/
GNU General Public License v3.0
1.35k stars 100 forks source link

Create vimb.spec #635

Closed adamthiede closed 3 years ago

adamthiede commented 4 years ago

This is a spec file to allow for building of vimb into an rpm. I've tested it and it works on Fedora 32/33/Rawhide.

fanglingsu commented 3 years ago

@elagost Thank you for this patch. But I do not want to put build files into the project that relate to a specific packet manager or build system. Could you please write here how a rpm package is build using this spec file. Then can I put this to the web page. But I'll not put it into the code.

adamthiede commented 3 years ago

I appreciate that you do have an opinion on this, and I think it's a good one. Thank you for the response. The Fedora Project's documentation on building RPM files does a better job than I could at explaining how to use specfiles. What I do: download the appropriate version's .tar.gz and the spec file into the same folder, run fedpkg --release f33 local (replace 33 with the current version of Fedora) and an .rpm is produced.

AloisMahdal commented 3 years ago

@elagost nice job with the specfile. Have you considered maintaining the package for Fedora? If that succeeded, all @fanglingsu would need to say on the webpage is that the package is in Fedora.

adamthiede commented 3 years ago

Have you considered maintaining the package for Fedora?

I've considered it and would like to do it, but it's just not something I've bothered to sit down and do yet. Seems like a large initial time investment to get started.

fanglingsu commented 3 years ago

@elagost I close this because packages to not belong into the project. But I there is a package I'd be happy to link it on the web page and the README.