---
- branch: MAIN
  date: Fri Apr 21 21:07:09 UTC 2017
  files:
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/ruby-globalid/DESCR
    pathrev: pkgsrc/devel/ruby-globalid/DESCR@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/ruby-globalid/Makefile
    pathrev: pkgsrc/devel/ruby-globalid/Makefile@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/ruby-globalid/PLIST
    pathrev: pkgsrc/devel/ruby-globalid/PLIST@1.1
    type: added
  - new: '1.1'
    old: '0'
    path: pkgsrc/devel/ruby-globalid/distinfo
    pathrev: pkgsrc/devel/ruby-globalid/distinfo@1.1
    type: added
  id: 20170421T210709Z.81ab4de78397c00edcbcea667de8bbbbfeea0542
  log: |
    Import ruby-globalid-0.4.0 as devel/ruby-globalid

    A Global ID is an app wide URI that uniquely identifies a model
    instance.  This is helpful when you need a single identifier to
    reference different classes of objects.  One example is job
    scheduling. We need to reference a model object rather than serialize
    the object itself. We can pass a Global ID that can be used to locate
    the model when it's time to perform the job. The job scheduler doesn't
    need to know the details of model naming and IDs, just that it has a
    global identifier that references a model.  Another example is a
    drop-down list of options, consisting of both Users and
    Groups. Normally we'd need to come up with our own ad hoc scheme to
    reference them. With Global IDs, we have a universal identifier that
    works for objects of both classes.
  module: pkgsrc
  subject: 'CVS commit: pkgsrc/devel/ruby-globalid'
  unixtime: '1492808829'
  user: minskim