On Wed, Jan 22, 2014 at 12:39:27PM -0600, Rob Browning wrote:
> Agustin Martin writes:
>
> > Did not test in depth, but I think the add-on state files state files
> > could be recreated from /usr/lib/emacsen-common/packages/install in
> > case emacsen-common is installed for the first time (i.e.,
Agustin Martin writes:
> I may be wrong, but if add-on-depending-on-add-on-1 depends on add-on-1 dpkg
> should care of configuring add-on-1 first. However, there is no warranty
> about unpack ordering.
No, of course -- I think you're right, and I believe that was part of my
reasoning when workin
[Apologies for any duplication: resending because the previous cc list
had been truncated.]
Modestas Vainius writes:
> I suggest that you bump policy version to 3 since current policy is probably
> going to be nothing like v2.
We could, though I hadn't been planning on it since these changes
Rob Browning writes:
> However, to demonstrate why I'm beginning to think the current approach
> may be unworkable, consider the case where no emacsen-related packages
> are installed and someone runs this:
>
> apt-get install emacs24 add-on-depending-on-add-on-1 add-on-1
>
> What should happen
Agustin Martin writes:
> Did not test in depth, but I think the add-on state files state files
> could be recreated from /usr/lib/emacsen-common/packages/install in
> case emacsen-common is installed for the first time (i.e., not
> upgraded). Since emacs flavours depend on emacsen-common they sho
--
Stephane Crivisier
On Mon, Jan 20, 2014 at 2:43 AM, Rob Browning
wrote:
> Recently I've been fixing some non-trivial problems I introduced in
> emacsen-common 2.0.0 -- and to finish fixing them it looks like it may
> be best to change (and augment) some of the add-on package requirements.
>
Hi Rob
It looks like your proposal is the best way forward, so I am in favour of
adding this dependency in all the Emacs-dependent packages.
BR
--
Danai
On 20 January 2014 14:20, Stephane Crivisier wrote:
> --
> Stephane Crivisier
>
>
> On Mon, Jan 20, 2014 at 2:43 AM, Rob Browning wrote:
2014/1/20 Rob Browning :
>
> Recently I've been fixing some non-trivial problems I introduced in
> emacsen-common 2.0.0 -- and to finish fixing them it looks like it may
> be best to change (and augment) some of the add-on package requirements.
>
> Originally, I'd really tried to make it so that as