I had to make a mod to the P4DTI that made it look for new Bugzilla entries - without it, P4DTI would never see new entries and propagate them over to P4.

" and bugs_activity.fieldid is null" # NO recent activity

Also, there's apparently a slight bug with the to-string transformation for inserting into MySQL, where a date (as opposed to a string) is passed into the routine.

I had to make a mod to the P4DTI that made it look for new Bugzilla entries - without it, P4DTI would never see new entries and propagate them over to P4. Also, there's apparently a slight bug with the to-string transformation for inserting into MySQL, where a date (as opposed to a string) is passed into the routine.

Other than that, everything seems to work.

I've attached my changes to the standard distro of bugzilla.py.

-Matt Albrecht SQA Engineer Zilliant, Inc

Matt Albrecht had modified bugzilla.py from release 1.1.1. Here are the changes he made:

224,227c224,232 < if (type(value) != types.StringType): < # "Given '%s' when expecting a string." < raise error, catalog.msg(105, str(value)) < return "'" + self.db.escape_string(value) + "'"

---

308d312 < 371d374 < 622d624 < 739a742,753

795c809 < bugs = changed + new_and_touched

---

--__--__--

Message: 3 From: davi...@redspark.com To: perforce-user at perforce.com Date: Fri, 3 Aug 2001 08:51:42 -0700 Subject: [p4] Code reuse: how to convert VSS shares to perforce equivalent?

I am in the throes of converting from VSS to Perforce. One of my user
community, a VSS guru, uses the "share" capability of VSS. This is essentially
the CM version of unix links - that is, a file is "shared" among multiple
directories and is really the same file - has the same version history etc, but
is present as multiple but always-identical copies of itself in each directory
that participates.

My developer uses this to do code reuse. He has a library directory, and
essentially every file in it is shared into each application directory. That
application (developed under Visual Studio) uses the library file as any other
file. Additionally, Visual Studio seems to know about VSS' sharing capability,
and in its integration with the development system, is willing to share files
from one project with another.

Is there a reasonable way to emulate this using Perforce?

If not, doesn't code reuse usually get accomplished with DLLs or LIBs?

-d

--__--__--

Message: 4 Date: Fri, 03 Aug 2001 12:18:22 -0400 To: david.hildebrandt at redspark.com, perforce-user at perforce.com From: Stephen Vance <steve at vance.com> Subject: Re: [p4] Code reuse: how to convert VSS shares to perforce equivalent?

At 08:51 AM 8/3/2001 -0700, david.hildebrandt at redspark.com wrote:

Two techniques:

Put the common code in its own area of the depot and integrate it into each project that uses it. This allows better control of how project-specific changes get approved and migrated back to the truly shared code base.

A more VSS-like approach would be to map the common code into the clients for each project. Everyone modifies it directly.

Ideally, yes. Unfortunately, many organizations don't have the manpower, organization, discipline, regulatory desire, etc. (lots of potential reasons) to have a distinct maintenance cycle for shared core code. This reduces the overhead for a common code base, but also facilitates the introduction of core code changes that work well for one project, but break compatibility for projects other than the one in which the code was changed.

Also, sometimes build environments aren't sufficiently mature to support true modularization. This is a combination of native tool capability and how the tools are implemented. Most build tools, including Visual Studio projects and make, allow you to do that kind of thing, but only through lots of implementation effort on your part.

Steve

Stephen Vance mailto:steve at vance.com http://www.vance.com/

--__--__--

End of perforce-user Digest