*Synopsis*: consolidations should use shared transforms for packaging

CR 6960216 changed on Jun 11 2010 by <User 1-5Q-1267>

=== Field ============ === New Value ============= === Old Value =============

See Also               6951274                                                
====================== =========================== ===========================

     
*Change Request ID*: 6960216

*Synopsis*: consolidations should use shared transforms for packaging

  Product: solaris
  Category: consolidation
  Subcategory: os-net-pkgs
  Type: RFE
  Subtype: 
  Status: 1-Dispatched
  Substatus: 
  Priority: 4-Low
  Introduced In Release: 
  Introduced In Build: 
  Responsible Engineer: <User 1-5Q-313>
  Keywords: 

=== *Description* ============================================================
Perhaps there is a better home for this, but consolidation/os-net-pkgs seems 
like one logical place...

As the various Solaris consolidations move to IPS, it would be nice if they had 
a set of shared pkgmogrify(1m) transforms that could be consistently applied 
across packages generated by all consolidations.  ON, X, and SFW each have or 
are developing sets of transforms that they apply to package manifests during 
packaging.  It seems to me that rather than having each consolidation or 
packager generate all of their transforms in a vacuum, we could create a set of 
shared transforms that we deliver to a common location 
(/usr/share/pkg/transforms/) for all to use.  This would help in generating 
consistent package sets that adhere to a common standard.

These transforms should minimally address
        default attributes for files and directories under common paths
        augmenting actions for paths the require restart_fmri actions
        augmenting actions to include facet tags for locale, docs, and devel 
paths

In some cases, consolidations will have transforms that generally apply only to 
them, but they may wish to share for the odd package outside of their 
consolidation to use to maintain consistentcy with them.  For example:
ON delivers the SMF service for manifest import and RBAC fragment assembly.  
They would likely want to share the following actions:

  # SMF service manifests
  <transform file path=(var|lib)/svc/manifest/.*\.xml$ -> \
      default restart_fmri svc:/system/manifest-import:default>

  # RBAC file fragments
  <transform file path=etc/security/[^/]+_attr.d/.+ -> \
      default restart_fmri svc:/system/rbac:default>
  <transform file path=etc/user_attr.d/.+ -> \
      default restart_fmri svc:/system/rbac:default>

JDS supplies a service for updating the desktop mime cache and might want to 
supply the following actions:
  # GNOME desktop files
  <transform file path=usr/share/applications/.*\.desktop$ -> \
      default restart_fmri 
svc:/application/desktop-cache/desktop-mime-cache:default>

X supplies a service to update the font cache and might want to supply the 
following actions:
  # Fonts and font configuration
  <transform file path=etc/fonts/conf\.(avail|d)/.+ -> \
      default restart_fmri svc:/application/font/fc-cache:default>
  <transform file path=usr/share/font/.+ -> \
      default restart_fmri svc:/application/font/fc-cache:default>

G11N delivers various localizations and would want to define facet tags for the 
various locale specific paths:
  <transform dir file link hardlink path=.*/locale/(.+)(\..+){0,1}(/.+){0,1}$ 
-> \
      default facet.locale.$1 true>

The point is that each consolidation will likely have pieces that relate 
directly to the software and services they deliver and as a result they should 
be able to deliver common transforms to aid external (to their consolidation) 
consumers and packagers in getting their packaging correct.

*** (#1 of 1): 2010-06-10 16:32:02 GMT+00:00 <User 1-5Q-12691>


=== *Public Comments* ========================================================

=== *Workaround* =============================================================

=== *Additional Details* =====================================================
        Targeted Release: solaris_nevada
        Commit To Fix In Build: 
        Fixed In Build: 
        Integrated In Build: 
        Verified In Build: 
  See Also: 6951274
  Duplicate of: 
  Hooks:
        Hook1: 
        Hook2: 
        Hook3: 
        Hook4: 
        Hook5: 
        Hook6: 
  Program Management: 
  Root Cause: 
  Fix Affects Documentation: No
  Fix Affects Localization: No

=== *History* ================================================================
        Date Submitted: 2010-06-10 16:32:02 GMT+00:00
        Submitted By: <User 1-5Q-12691>

        Status Changed    Date Updated                  Updated By


=== *Service Request* ========================================================
        Impact: Limited
        Functionality: Nonessential
        Severity: 5
        Product Name: solaris
        Product Release: solaris_nevada
        Product Build: 
        Operating System: snv_141
        Hardware: generic
        Submitted Date: 2010-06-10 16:32:02 GMT+00:00


=== *Multiple Release (MR) Cluster* - 0 ======================================

_______________________________________________
on-ips-dev mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/on-ips-dev

Reply via email to