Debian.GenBuildDeps

Figure out the dependency relation between debianized source directories. The code to actually solve these dependency relations for a particular set of binary packages is in Debian.Repo.Dependency.

Documentation

data DepInfo

This type describes the build dependencies of a source package.

Constructors

DepInfo

Fields

• sourceName :: SrcPkgName

  source package name

• relations :: Relations

  dependency relations

• binaryNames :: [BinPkgName]

  binary dependency names (is this a function of relations?)

• depSet :: Set BinPkgName

  Set containing all binary package names mentioned in relations

• binSet :: Set BinPkgName

  Set containing binaryNames

Instances

Eq DepInfo

Methods

(==) :: DepInfo -> DepInfo -> Bool

(/=) :: DepInfo -> DepInfo -> Bool

Show DepInfo

Methods

showsPrec :: Int -> DepInfo -> ShowS

show :: DepInfo -> String

showList :: [DepInfo] -> ShowS

sourceName' :: HasDebianControl control => control -> SrcPkgName

source package name

relations' :: HasDebianControl control => control -> Relations

dependency relations

binaryNames' :: HasDebianControl control => control -> [BinPkgName]

binary dependency names (is this a function of relations?)

Preparing dependency info

buildDependencies :: HasDebianControl control => control -> DepInfo

Return the dependency info for a source package with the given dependency relaxation. |According to debian policy, only the first paragraph in debian/control can be a source package http://www.debian.org/doc/debian-policy/ch-controlfields.html#s-sourcecontrolfiles

type RelaxInfo = SrcPkgName -> BinPkgName -> Bool

Given a source package name and a binary package name, return False if the binary package should be ignored hwen deciding whether to build the source package. This is used to prevent build dependency cycles from triggering unnecessary rebuilds. (This is a replacement for the RelaxInfo type, which we temporarily rename OldRelaxInfo.)

relaxDeps :: RelaxInfo -> [DepInfo] -> [DepInfo]

Remove any dependencies that are designated "relaxed" by relaxInfo.

Using dependency info

data BuildableInfo a

Constructors

BuildableInfo

Fields

• readyTargets :: [ReadyTarget a]
• allBlocked :: [a]

CycleInfo

Fields

• depPairs :: [(a, a)]

data ReadyTarget a

Constructors

ReadyTarget

Fields

• ready :: a

  Some target whose build dependencies are all satisfied

• waiting :: [a]

  The targets that are waiting for the ready target

• other :: [a]

  The rest of the targets that need to be built

buildable :: forall a. (a -> DepInfo) -> [a] -> BuildableInfo a

Given an ordering function representing the dependencies on a list of packages, return a ReadyTarget triple: One ready package, the packages that depend on the ready package directly or indirectly, and all the other packages.

compareSource :: DepInfo -> DepInfo -> Ordering

This is a nice start. It ignores circular build depends and takes a pretty simplistic approach to or build depends. However, I think this should work pretty nicely in practice.

Obsolete?

orderSource :: (a -> a -> Ordering) -> [a] -> [a]

Given a list of packages, sort them according to their apparant build dependencies so that the first element doesn't depend on any of the other packages.

genDeps :: [FilePath] -> IO [DebianControl]

Return the dependency info for a list of control files.

failPackage :: Eq a => (a -> a -> Ordering) -> a -> [a] -> ([a], [a])

Remove any packages which can't be built given that a package has failed.

getSourceOrder :: FilePath -> IO [SrcPkgName]

One example of how to tie the below functions together. In this case fp is the path to a directory that contains a bunch of checked out source packages. The code will automatically look for debian/control. It returns a list with the packages in the order they should be built.