Mike Kupfer wrote:
I went through the open bugs in solaris/consolidation/os-net-misc and
...os-net-tools to see if there were build issues that need to be fixed
prior to moving to Mercurial.

There were a few variations on "make clobber doesn't delete everything
it's supposed to".  I wouldn't be surprised if they overlap each other.
I've marked them all with the hg_trans keyword.  Since they're not
showing up in b.o.o, I've listed them here:

    6414855 make clobber doesn't
    6290199 idn_offsets.h isn't removed by clobber
    4968835 workspace built on sparc fails to build on x86
    4058577 make clobber of ON does not remove 217 derived files

Keywords will show up next time b.o.o syncs.

Fortunately, I only found 3 other possible stoppers:

    4758439 some files use "current date" sccs keywords
    6495337 warlock should work when usr/closed source tree does not exist
    6446689 webrev(1) needs Mercurial support

6495337 isn't exactly a stopper, since warlock is only available inside Sun.
I'd dearly like to see that change, however.

If it becomes available outside, I'd previously said I'd look into making it work without usr/closed so we can use it. That still stands.

If I understand 4758439 correctly, some packages are baking SCCS
keywords into their pkginfo metadata.  I think we can just rip that out
and not try to replace it.

Agree

For 6495337, I tend to think it should not be a stopper, because we can
just tell internal folks to have both the open and closd tree present.
(And AFAIK warlock is not available for the external folks.)  But I
wanted to mention it in case anyone wants to argue differently.

See above, I agree.  But I *really* want warlock to be available outside.
I personally see it being available as a prerequisite to:

6493270 nightly.sh should make it easier to run warlock.

So while it's not a stopper, I'd really like to figure out if we can get warlock available to all of us and working, either way.

(I've asked about it before, but didn't really get much in the way of answer)

For 6446689, I'm not sure where we are with webrev and Mercurial.  There
are several unresolved webrev-related bugs in bugs.grommit.com.  I'm
planning to tag this one with hg_trans, just to keep the paperwork
consistent.

Yes.

-- Rich

_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org

Reply via email to