lp://staging/~kgoetz/+junk/civicrm-drupal

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

67. By root <root@civicrmdev> on 2014-05-01

Fix files-excluded in d/copyright

This list is now complete (i think) but still not able to be used. It requires
us to go through all the packages and make sure the ones we have do in fact
work in stead of the packages shipped by upstream.
Tricky.

66. By root <root@civicrmdev> on 2014-04-29

Updating control with devscripts version

Because of using files excluded we need at least 2.13.5 - when it was released.

65. By root <root@civicrmdev> on 2014-04-29

Adding files excluded to copywrite file

This is supported, but not by uscan i have available. Whatever. It cleans
up my rules file by a lot of lines.

64. By root <root@civicrmdev> on 2014-04-29

Move all repacking out of rules to uscan/files-excluded

When I say all its a bit of a lie since there is some repacking left because
we can't simply kill off json.js and have to keep its parent directory. The
vast majority is out now, just a few extra steps because of backbone/json.js.

Only problem: We need a newser uscan then is available in backports. Thats a
pain but since any package upload would focus on sid anyway whats the point?

63. By root <root@civicrmdev> on 2014-04-29

Fix watch file so it works through redirector

This took quite some searching but i managed to track down a good instruction
at last - annoyingly in the lintian warning for not having it.

62. By root <root@civicrmdev> on 2014-04-22

Adding our first patch working around hard coding of paths

This is a basic patch, not ready for prime time. Its not been tested or
had its dep3 headers added and is here as much to remind about the need to fix
this particular bit of code as it is to actually do the fixing.

61. By root <root@civicrmdev> on 2014-04-22

Add notes against all packages in versions file

I've gone and worked through the versions file trying to figure out what we
can and can't trivially remove. Good news: Lots is trivial to remove. Bad
news: There are a number of packages with custom changes or where the versions
aren't very close (eg using a deprecated library).

I've not tested any of these stated removals, they should really say 'remove'
not 'removed'

60. By root <root@civicrmdev> on 2014-04-22

Update some pacakge.list entries

These are new info now i've gone through the versions file and re looked
at all the possabilities - seems we have some more packaging to do.

59. By root <root@civicrmdev> on 2014-04-22

Adding upstreams VERSIONS file as packages.VERSIONS

This file should be used in conjunction with packages.list to see what needs
to be added/removed and find out which packages have been altered.
It also contains handy steps for how to update the custom packages and detect
any changed versions - great for what I'm about to try.

58. By root <root@civicrmdev> on 2014-04-22

Update packaging to support no bundled software

This is a rather large update since it documents all the changes required
to unbundle external software from civi (i think...).
* control has been updated to list the removed packages as dependencies. Note
  that not all of these packages are installable (or don't completely exist)
  so the move is rather optomistic.
* packages.list has been updated with information on where all the packages
  can be found. Some are available as debs, others only as bzr branches still.
  Also note: if the dependencies bundled their dependencies they may have been
  missed.
* rules get-orig-source repack section now removes all the packages listed
  above; apart from locally modified packages it would make sense to remove the
  whole dir in one hit

This update doesn't factor in custom changes made to the bundled packages so
some may not *actually* be removable at this stage.