pkg-TODO could be thought of as 'pkg-CHANGES that have yet to take
	place'.

	Both locations work for different reasons, I do not see
	significant technical merit fo rone vs the other, so I'll go
	with the core members vote :)

	pkgsrc/TODO it is - does someone want to take one of their
	exiting lists and commit it to start things rolling?

		David/absolute		-- www.netbsd.org: No hype required --


On Tue, 1 May 2001, Alistair Crooks wrote:

> I dislike the way that pkg-CHANGES is divorced from the pkgsrc-changes
> mailing list, but see no way of curing that, short of moving it to the
> main pkgsrc tree. I really don't want to go there.
>
> I'm not sure what you'd gain from the close proximity of the pkg-CHANGES
> and pkg-TODO files.
>
> Regards,
> Alistair
>
> On Mon, Apr 30, 2001 at 05:43:08PM +0100, David Brownlee wrote:
> > 	Here is where I do an 'about face'.
> >
> > 	I think pkg-TODO should probably go in the same location as
> > 	pkg-CHANGES. I'd actually prefer them both in a subdir of
> > 	pkgsrc, but I can understand them 'doc' making more sense.
> >
> > 	Aside: I wonder how many more kernel CHANGES entries we would get
> > 	if we had a file in syssrc for them...
> >
> > 		David/absolute		-- www.netbsd.org: No hype required --
> >
> >
> > On Mon, 30 Apr 2001, David Brownlee wrote:
> >
> > > 	Does anyone have any objections to adding one - it could include
> > > 	a list of packages, urls, and submittors, and a second section
> > > 	for suggested pkgsrc enhancements.
> > >
> > > 	If its OK to add, where should it live?
> > >
> > > 	pkgsrc/TODO		Obvious
> > > 	pkgsrc/mk/TODO		Clutters the top level less
> > > 	doc/pkg-TODO		More awkward to update
> > >
> > >
> > > 		David/absolute		abs@formula1.com
> > >
> > >
> >
>