[22] in athena10

home help back first fref pref prev next nref lref last post

Repository organization

daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Dec 27 13:12:13 2007

Date: Thu, 27 Dec 2007 13:12:01 -0500
Message-Id: <200712271812.lBRIC16u012074@equal-rites.mit.edu>
From: Greg Hudson <ghudson@MIT.EDU>
To: athena10@MIT.EDU

Side note: I added andersk and tabbott to source-commits.  The same
list is used for CVS commits for the athena 9.4 repository; that's
garbage mail for you but there shouldn't be too much of it.

Here's my proposed organization:

  Repository dir		Ganked from
  --------------		-----------
  debathena/scripts		/mit/debathena/bin
  debathena/config		/mit/debathena/packages/config
  debathena/debathena		/mit/debathena/packages/debathena
  debathena/meta		/mit/debathena/packages/meta
  debathena/third		/mit/debathena/package/third

Not ganked:

  /mit/debathena/packages/athena - Instead we put debian subdirs in
  athena/bin/blah.

  /mit/debathena/packages/manual-config - These are just empty
  packages with provides and conflicts declarations, right?  Are they
  auto-generated?  If so we presumably don't need sources for them.

  /mit/debathena/packages/contrib - I can't find evidence that this
  stuff is actually built and deployed anywhere; correct me if I'm
  wrong.

After snapshotting stuff, I plan to work on adding a rules file to
debathena-config-build-common to handle the lack of boilerplate
autotools goo in athena source directories, following tabbott's
suggestion.

home help back first fref pref prev next nref lref last post