[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Package tree structure



I am currently working on a channel system for system-config-packages
similar to the one used by red-carpet.

As such, I would like verify the intended download.fedora.redhat.com
hierarchy.

The root level will contain the overall package sets. 
[core|extras|alternatives|3rd party|...]

Each of these package sets will contain subsets of packages in different
states of development.  The numbered release will freeze at
approximately 2-3 month intervals.  Development and Testing are rolling
releases.
[1|2|...|development|test]

Each of these Releases may be compiled for a number of archs.  
[i386|i386_64|...]

Additionally, the numbered release will have updates and possibly legacy
packages.  Updates will continue for approximately 12 months and the
legacy will continue as long as maintainers are interested
[updates|legacy]


This should result in a tree looking as such.
fedora
  -core
    -1
      -i386
      -i386_64
      -updates
        -i386
      -legacy
        -i386 
    -2
      -i386
      -i386_64
    -development
      -i386
      -i386_64
    -test
       -i386
       -
  -extras
    -1
      -i386
    -2
      -i386

There is already some deviance from this tree
with 
  -core
    -updates
      -1
      -testing

Because each numbered release will contain updates, updates should be a
child of it's numbered parent.  -updates/test either needs to merge into
-test or -1/updates.

I don't intended to too uptight, but setting standards will help make
the tree more navigable for everyone.

Thanks
Dave Farning




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]