Ticket #258 (new task)

Opened 12 years ago

Last modified 11 years ago

split out pyhesiodfs from debathena pyhesiodfs configuration

Reported by: tabbott Owned by:
Priority: normal Milestone: The Distant Future
Component: -- Keywords:
Cc: kcr Fixed in version:
Upstream bug:

Description

We should debathena-pyhesiodfs into the generic software and configuration as two separate things.

That way people who aren't using Debathena can just grab pyhesiodfs and not get annoyed by our dependencies.

Change History

comment:1 Changed 11 years ago by jdreed

  • Milestone set to The Distant Future

comment:2 Changed 11 years ago by broder

Is this just referring to the debathena-hesiod-config dependency? If that's all we care about, we can just drop the dependency from pyhesiodfs since pyhesiodfs is pulled in by metapackages that already depend on hesiod-config

comment:3 Changed 11 years ago by andersk

Probably also /etc/fuse.conf.debathena and the initscripts.

comment:4 Changed 11 years ago by kcr

Note also that libhesiod has a valid configuration baked in.

Note: See TracTickets for help on using tickets.