link file in develop-eggs not deleted when an egg is removed from the develop list in buildout.cfg

Bug #408608 reported by David Hostetler
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Buildout
Incomplete
Undecided
Unassigned

Bug Description

It appears that when buildout is run, the contents of the develop-eggs directory isn't updated to be consistent with the specific list of source eggs listed in the 'develop=' value of the buildout.cfg (or whatever effective config is used when buildout is run). Namely - if a source egg is removed from that list, buildout *SHOULD* remove the link file for that egg from the develop-eggs directory, but it doesn't. Failure to remove the link file causes buildout to also fail to fetch and otherwise incorporate the normal release version of the egg (assuming one is available).

It is my impression that the develops-eggs folder (like fake-eggs, and the parts and var folders, etc..) is among the set of things that are supposed to be treated as completely transient pieces of output resulting from running buildout, and that anytime buildout is run, those pieces of output should be made completely consistent with whatever configuration was in effect when buildout was run.

Cheers,

David Hostetler
<email address hidden>

Revision history for this message
Jim Fulton (jim-zope) wrote : Re: [Bug 408608] [NEW] link file in develop-eggs not deleted when an egg is removed from the develop list in buildout.cfg

On Mon, Aug 3, 2009 at 5:47 PM, David Hostetler<email address hidden> wrote:
> Public bug reported:
>
> It appears that when buildout is run, the contents of the develop-eggs
> directory isn't updated to be consistent with the specific list of
> source eggs listed in the 'develop='  value of the buildout.cfg (or
> whatever effective config is used when buildout is run).  Namely - if a
> source egg is removed from that list, buildout *SHOULD* remove the link
> file for that egg from the develop-eggs directory, but it doesn't.
> Failure to remove the link file causes buildout to also fail to fetch
> and otherwise incorporate the normal release version of the egg
> (assuming one is available).
>
> It is my impression that the develops-eggs folder (like fake-eggs, and
> the parts and var folders, etc..) is among the set of things that are
> supposed to be treated as completely transient pieces of output
> resulting from running buildout, and that anytime buildout is run, those
> pieces of output should be made completely consistent with whatever
> configuration was in effect when buildout was run.

Buildout does normally remove egg link files from develop-eggs when
values are removed from the develop option. There are tests to verify
this.

Please give a set of steps to reproduce this. Please run these steps
yourself to make sure that they lead to the situation you report.

Jim

--
Jim Fulton

Revision history for this message
David Hostetler (dahoste) wrote :

Roger that -- I will attempt to isolate and verify.

Jim Fulton (jim-zope)
Changed in zc.buildout:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.