From Fedora Project Wiki
Line 44: Line 44:


* YUM repository reader
* YUM repository reader
** repoquery --whatprovides is to slow due to reinitialization
** <code>repoquery --whatprovides</code> is to slow due to reinitialization
* Gather boot-strapped dependencies from local SRPMs
* Gather boot-strapped dependencies from local SRPMs
* Use graph algorithms to identify cycles
* Use graph algorithms to identify cycles

Revision as of 13:16, 2 April 2014


Version normalization

  • Take over dependency generator
  • Macros for simplified packaging
    • the version translator
    • the perl() wrapper
    • common snippets for EU::MM, Module::Build, etc.
  • version->parse->normal normalization in macros and generator
  • Normalize RPM package version?

Dependency generator

  • Tests
  • Tests
  • Support no, base, parent, Moose's with, POE's extensions, Test::Requires, other frameworks, see Module::ScanDeps::scan_chunk()
  • Receive explicit Requires from spec file to merge them with generated ones
  • Refactoring

Fedora-Rebuild

  • Optimize pure-perl resolver
  • Implement hawkey-based resolver
    • XS wrapper for hawkey
    • YUM repository filter for Fedora-Rebuild dependency filter
    • YUM repostory downloader
    • Augment Fedora-Rebuild to download YUM repository, filter it, and do hawkey queries over it.
  • Copr mode
    • Copr is missing way how to retrieve binary package made of only exact source package
    • Select binary packages from Copr's YUM repository
    • Requires YUM downloaded and metadata parser

Continuous rebuilds

  • Fedmsg binding to Perl
  • Use fedmsg to gather updated packages
    • I have already GIT based checker
  • Use fedmsg to include new packages
  • Use fedmsg to exclude retired packages

Dependency cycle breaker

  • YUM repository reader
    • repoquery --whatprovides is to slow due to reinitialization
  • Gather boot-strapped dependencies from local SRPMs
  • Use graph algorithms to identify cycles
  • Semi-automated recommendation for cycle break-points

YUM repository parser

  • YUM metadata downloader
  • YUM metadata reader
  • YUM metadata filter/writer
  • YUM package downloader

Macros for simplified packaging

  • Version normlizer
  • perl() wrapper
    • This will mask SCL modifications
  • Dependency filter abstraction
    • One syntax for Fedora and EPEL
    • One syntax for SCL
  • Provide standard EU::MM, Module::Build, Module::Bild::Tiny, &c. %build and %install implementations
  • Standard implementations for CPAN packages
    • URL
    • Sourece0
    • %prep
  • Pack files scriptlets editor
    • Allow Fatpacker and inc::Module::Build bundler to work on packaged modules
  • Mark POD files as documentation

Spec file generator

  • Fork cpan2spec
  • Static dependency analysis
  • Dynamic dependency analysis
  • Compare analyses against RPM package
    • Comment annotations in spec
    • Structured build-, run-, test- dependencies
  • Differences calculator
    • Useful when upgrading a package
  • False provides checker
    • RPM package should not provide privately redefined modules

Fedora Upstream monitoring

  • Monitor upstram on our own if Fedora's system will not be improved
    • The maintainer wants CPAN wildcard
  • Monitor all RPM packages
    • Update them before each mass rebuild

Developer Assistant

  • Templates for standard build systems
  • Templates for web frameworks

Upstream monitoring

  • Not all packages are registered in Fedora Upstream Monitoring service
  • Not all packagers upgrades
  • Monitor upstream on our own
    • Use CPAN
    • Adjust versions where done in Fedora
    • File bugs or do the upgrade directly or spam perl-devel
  • CPAN mirrors provides signed digests of CPAN distributions
    • Verify them against Fedora look-aside cache
    • Add the check into spectool(1)

Perl Next

  • While perl is a base package, other CPAN code will go into server or workstation. We need to be ready and implement Next requirements
  • I propose to delay perl 5.20 upgrade to Fedora 22.