Annotation of wikisrc/projects/project/pkgsrc_binpkg_depends.mdwn, revision 1.4

1.1       jmmv        1: [[!template id=project
                      3: title="Add dependency information to binary packages"
                      5: contact="""
                      6: [tech-pkg](
                      7: """
                      9: mentors="""
                     10: [Thomas Klausner](
                     11: """
1.2       jmmv       13: category="pkgsrc"
                     14: difficulty="hard"
1.1       jmmv       15: duration="3 months"
                     17: description="""
                     18: Change infrastructure so that dependency information (currently in files) is installed with a binary package and is used from there
                     20: This is not an easy project.
                     22: pkgsrc currently handles dependencies by including files spread over pkgsrc. The problem is that these files describe the current state of pkgsrc, not the current state of the installed packages.
                     24: For this reason and because most of the information in the files is templated, the files should be replaced by the relevant information in an easily parsable manner (not necessarily make syntax) that can be installed with the package.
                     25: Here the task is to come up with a definitive list of information necessary to replace all the stuff that's currently done in files (including: dependency information, lists of headers to pass through or replace by buildlink magic, conditional dependencies, ...)
                     27: The next step is to come up with a proposal how to store this information with installed packages and how to make pkgsrc use it.
                     29: Then the coding starts to adapt the pkgsrc infrastructure to do it and show with a number of trivial and non-trivial packages that this proposal works.
                     31: It would be good to provide scripts that convert from the current state to the new one, and test it with a bulk build.
                     33: Of course it's not expected that all packages be converted to the new framework in the course of this project, but the further steps should be made clear.
1.3       mspo       34: 
                     35: goals/milestones:
1.4     ! leot       36: 
1.3       mspo       37: * invent a replacement for files, keeping current features
                     38: * demonstrate your new tool as a replacement including new features
                     39: * execute a bulk build with as many packages as possible using the new buildlink
1.1       jmmv       41: """
                     42: ]]
                     44: [[!tag gsoc]]

CVSweb for NetBSD wikisrc <> software: FreeBSD-CVSweb