Re: More package breakage
On Sun, 2003-02-09 at 02:37, Steve Youngs wrote:
SJT> Whoever played with the mule-ucs package recently arranged
for
SJT> one ChangeLog to overwrite another, and cp complains:
I'm sure that whoever did it didn't want this outcome. It's just a
pity that mule-ucs/ChangeLog doesn't mention anything about it. Oh
well, the guilty party is probably feeling suitably guilty right
now.:-)
Well, looks like I've been committing patches there recently, but on
behalf of others, and I don't see why any of those changes would have
caused this. Maybe it's related to other recent changes in packages
build system.
Anyway, the problem is that 'lisp/ChangeLog' is listed in
$EXTRA_SOURCES.
Hmm, according to CVS, that has there since The Very Beginning of
mule-ucs.
Anything in that var is copied to:
${XEMACS_INSTALLED_PACKAGES_ROOT}/${MULE_INSTALLED_PACKAGES_ROOT}/lisp/mule-ucs/
$(STAGING)/lisp/$(PACKAGE), I suppose you meant to say... but isn't that
what has always happened? I'm curious why nobody has seen this before.
I'd fix it by renaming lisp/ChangeLog to lisp/ChangeLog.upstream
and
change $EXTRA_SOURCES accordingly.
That isn't quite a real fix, lisp/ChangeLog is not only a "upstream"
one, and renaming it will cause trouble with add-log and friends.
IMO, removing lisp/ChangeLog from EXTRA_SOURCES would be a better "fix"
for now. When making the discussed changes to installed package layouts
later(tm), this should be really taken care of.
--
\/ille Skyttä
scop at xemacs.org