Opened 8 years ago

Last modified 7 years ago

#12917 reopened enhancement

get_package_dependencies needs to be refactored — at Initial Version

Reported by: kallisti5 Owned by: kallisti5
Priority: normal Milestone: Unscheduled
Component: Kits/Package Kit Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Platform: All

Description

It appears the entire reason the url exists in the repo file (BRepositoryInfo blob) is to appease the get_package_dependencies binary. The requirements of get_package_dependencies could be greatly cleaned up.

Current Behaviour

get_package_dependencies takes in the following arguments:

get_package_dependencies then 'solves' the dependencies and links to where the package should be based on the url in repo.info.

get_package_dependencies seems to be the only thing that actually uses the url field in the repo.info / repo manifest. (this url field makes repo's unportable to other locations)

How it should work

  • A series of remote repo URL's are provided to the tool
    • Tool downloads repo manifest from each remote repo.
    • Tool now knows "where repos exist, and what packages they contain"
  • --
  • Every local hpkg file to be placed into the image.

Change History (1)

by kallisti5, 8 years ago

Attachment: output.txt added
Note: See TracTickets for help on using tickets.