Does anyone know what happened to the following *plague-0.5.0* programs?
File: ExtrasMultiLib.py Status: Entry Invalid File: ExtrasPushUtils.py Status: Entry Invalid File: extras-push-new Status: Entry Invalid File: extras-repobuild.py Status: Entry Invalid File: extras-repoview.py Status: Entry Invalid File: extras-sync Status: Entry Invalid
... they seem to have _disappeared_ from the extras-buildsys/utils module in the CVS tree..
Joe
On Tue, 2006-10-31 at 10:19 -0500, Joe Todaro wrote:
Does anyone know what happened to the following *plague-0.5.0* programs?
File: ExtrasMultiLib.py Status: Entry Invalid File: ExtrasPushUtils.py Status: Entry Invalid File: extras-push-new Status: Entry Invalid File: extras-repobuild.py Status: Entry Invalid File: extras-repoview.py Status: Entry Invalid File: extras-sync Status: Entry Invalid
... they seem to have _disappeared_ from the extras-buildsys/utils module in the CVS tree..
It looks like they changed somewhat, and migrated to extras-buildsys/utils/pushscript/
Dan
Joe
Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
fedora-buildsys-list-bounces@redhat.com wrote on 10/31/2006 10:38:59 AM:
On Tue, 2006-10-31 at 10:19 -0500, Joe Todaro wrote:
Does anyone know what happened to the following *plague-0.5.0* programs?
File: ExtrasMultiLib.py Status: Entry Invalid File: ExtrasPushUtils.py Status: Entry Invalid File: extras-push-new Status: Entry Invalid File: extras-repobuild.py Status: Entry Invalid File: extras-repoview.py Status: Entry Invalid File: extras-sync Status: Entry Invalid
... they seem to have _disappeared_ from the extras-buildsys/utils module in the CVS tree..
It looks like they changed somewhat, and migrated to extras-buildsys/utils/pushscript/
Thanks. Now I see it. Had to do a fresh checkout of the extras-buildsys tree to get it download.
Joe
Dan
Joe
Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
On Tue, 31 Oct 2006 10:19:37 -0500, Joe Todaro wrote:
Does anyone know what happened to the following *plague-0.5.0* programs?
File: ExtrasMultiLib.py Status: Entry Invalid File: ExtrasPushUtils.py Status: Entry Invalid File: extras-push-new Status: Entry Invalid File: extras-repobuild.py Status: Entry Invalid File: extras-repoview.py Status: Entry Invalid File: extras-sync Status: Entry Invalid
... they seem to have _disappeared_ from the extras-buildsys/utils module in the CVS tree..
They are not part of plague, they are not needed by plague, but they can still be found in CVS in the "pushscript" sub-directory.
[One of the primary reasons they have been moved there is the included copy of yum and the added configuration support. That makes it much easier to re-use the script for repositories other than Fedora Extras. The Config_Extras.py file becomes Config_PROJECTNAME.py (for customisation) and then either the scripts are run like "./Push.py PROJECTNAME options-here" or you create wrapper-scripts like the examples extras-push, extras-repobuild and so on, where the projectname can be filled in and activates the right Config file.]
fedora-buildsys-list-bounces@redhat.com wrote on 10/31/2006 11:20:25 AM:
On Tue, 31 Oct 2006 10:19:37 -0500, Joe Todaro wrote:
Does anyone know what happened to the following *plague-0.5.0*
programs?
File: ExtrasMultiLib.py Status: Entry Invalid File: ExtrasPushUtils.py Status: Entry Invalid File: extras-push-new Status: Entry Invalid File: extras-repobuild.py Status: Entry Invalid File: extras-repoview.py Status: Entry Invalid File: extras-sync Status: Entry Invalid
... they seem to have _disappeared_ from the extras-buildsys/utils
module
in the CVS tree..
They are not part of plague, they are not needed by plague, but theycan
still
be found in CVS in the "pushscript" sub-directory.
[One of the primary reasons they have been moved there is the included copy of yum and the added configuration support. That makes it much
easier
to re-use the script for repositories other than Fedora Extras. The Config_Extras.py file becomes Config_PROJECTNAME.py (for
customisation)
and then either the scripts are run like "./Push.py PROJECTNAME
options-here"
or you create wrapper-scripts like the examples extras-push, extras-repobuild and so on, where the projectname can be filled in and activates the right Config file.]
I very much appreciate the explanation.
Thank You, Joe
-- Fedora-buildsys-list mailing list Fedora-buildsys-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-buildsys-list
buildsys@lists.fedoraproject.org