File README.maintain of Package google-noto-fonts

Overview Repositories Revisions Requests Users Attributes Meta

File README.maintain of Package google-noto-fonts (Revision ef4b190ec5e3f8e501b7c03ea0c0238b)

Currently displaying revision ef4b190ec5e3f8e501b7c03ea0c0238b , Show latest

Last reviewed: 2024-05-01
1. Download the latest release tarball from here: https://github.com/notofonts/notofonts.github.io/releases
2. Rename the current specfile to old.spec then edit the versions in generate-specfile.sh and google-noto-fonts.spec.in
3. Run generate-specfile.sh to get the new specfile
  - generate-specfile.sh untars your tarball and then based on the folders in fonts, generates a specfile with every package being a folder
4. Compare the two specfiles with some sort of diffing program and note any added, deleted, or renamed packages
5. Push to your branch (osc ci) to see if the package builds, osc build is of limited use
   as your local vm will likely crash before the build is fully completed
6. If there are no noteworthy errors, then write the osc vc with the changes,
   push, then send the submit request (osc sr). If there are, then fix them first
   before submitting

If you need to change the specfile, you change it programmatically in generate-specfile.sh
 rather than directly edit google-noto-fonts.spec
That way the next person who runs the script does not need to redo your changes
Editing google-noto-fonts.spec.in however is fine

Places

File README.maintain of Package google-noto-fonts (Revision ef4b190ec5e3f8e501b7c03ea0c0238b)

Places