Next | Query returned 39 messages, browsing 31 to 40 | previous

History of commit frequency

CVS Commit History:


   2006-04-06 09:17:12 by Jeremy C. Reed | Files touched by this commit (26)
Log message:
Change BUILDLINK_DEPENDS.foo to BUILDLINK_API_DEPENDS.foo.

Change BUILDLINK_RECOMMENDED.foo to BUILDLINK_ABI_DEPENDS.foo.

As discussed on tech-pkg.
   2005-11-02 19:00:10 by Thomas Klausner | Files touched by this commit (85)
Log message:
"wip" is not a valid category -- please use the standard pkgsrc ones.

Remove wip from CATEGORIES, and guess category if wip was the only one
specified.
   2005-06-13 01:51:13 by Krister Walfridsson | Files touched by this commit (92)
Log message:
Change obsolete USE_X11 to include ../../mk/x11.buildlink3.mk instead.
   2005-04-11 23:11:48 by Todd Vierling | Files touched by this commit (1)
Log message:
Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used.

   2004-10-16 00:32:39 by Min Sik Kim | Files touched by this commit (1)
Log message:
Correct path to eet.

   2004-10-15 16:53:19 by Todd Vierling | Files touched by this commit (2)
Log message:
Update linkage to libltdl, which is now its own package.

Some of these packages probably don't use libltdl at all, but it's up to
the MAINTAINER to fix the .includes to pull in only what's actually needed.
   2004-10-13 11:01:35 by Min Sik Kim | Files touched by this commit (1)
Log message:
eet has been moved to pkgsrc.
   2004-09-23 07:59:33 by Johnny C. Lam | Files touched by this commit (1)
Log message:
Mechanical conversion to use LIBTOOLIZE_PLIST (which defaults to "yes" in
pkgsrc).  LIBTOOL_LA_FILES is no more.
   2004-09-16 19:41:00 by Peter Bex | Files touched by this commit (5) | Imported package
Log message:
Edje is a complex graphical design and layout engine. It provides a
mechanism for allowing configuration data to define visual elements in
terms of layout, behavior, and appearance.  Edje allows for multiple
collections of layouts in one file, allowing a complete set of images,
animations, and controls to exist as a unified whole.

Edje separates the arrangement, appearance, and behavior logic into
distinct independent entities.  This allows visual objects to share
image data and configuration information without requiring them to do
so.  This separation and simplistic event driven style of programming
can produce almost any look and feel one could want for basic visual
elements. Anything more complex is likely the domain of an application
or widget set that may use Edje as a conveneient way of being able to
configure parts of the display.


Next | Query returned 39 messages, browsing 31 to 40 | previous