Re: [urgent] Review container packager guidelines

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

 



On Thu, Feb 25, 2016 at 4:14 PM, Kushal Das <mail@xxxxxxxxxxxx> wrote:
> Around 6 weeks back Adam created a new trac ticket [1] about the
> container "Packager" guidelines. It is related to the work for layered
> image build process [2].


<https://fedoraproject.org/wiki/Changes/Layered_Docker_Image_Build_Service#Content_Tracking.2C_Automatic_Rebuilds>
mentions "But we don't want to block having the basic build service in
place on that; initially, updates will need to be initiated by the
container packager."

This begets 2 questions - (a) what is the means to identify the images
which have gone stale because packagers have not updated (b) how to
packagers receive notifications that the images would need to be
rebuilt



-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
_______________________________________________
cloud mailing list
cloud@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/cloud@xxxxxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Fedora General Discussion]     [Older Fedora Users Archive]     [Fedora Advisory Board]     [Fedora Security]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Mentors]     [Fedora Package Announce]     [Fedora Package Review]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Coolkey]     [Yum Users]     [Big List of Linux Books]     [Yosemite News]     [Linux Apps]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Asterisk PBX]

  Powered by Linux