This issue was migrated from Pagure Issue #971. Originally filed by mharmsen (@mharmsen) on 2014-04-17 21:02:18:
Assigned to nobody
This ticket was created in reponse to the question "What is the difference between pki/scripts and pki/base/scripts?"
This was the answer provided:
We used to have similar directories (e. g. - 'pki/dogtag/scripts' and 'pki/redhat/scripts' associated with the Dogtag and Red Hat themes respectively) which housed scripts primarily used for the legacy method of building individual RPMS and SRPMS (e. g. - pki-ca RPM and pki-ca SRPM as opposed to pki-ca RPM and pki-core SRPM). This separation allowed theme packages and their icons to reside in separate repositories and still be built utilizing the same core server/client pieces, as at that time, at least one theme was required and the themes were mutually exclusive.
Since we do not really ship any devel packages, the scripts under 'pki/base/scripts' were just meant for un-packaged development tools related to the core server/client pieces - similar to the 'pki/tools' directory which was created at a later date to house development tools which were not scripts.
Since Dogtag 10.x builds individual SRPMS which often contain numerous RPMS, the 'pki/scripts/' directory houses scripts used for building these and pertain to the PKI project as well as its default Dogtag theme.
It may make sense to re-organize and consolidate some of these directories.
This issue was migrated from Pagure Issue #971. Originally filed by mharmsen (@mharmsen) on 2014-04-17 21:02:18:
This ticket was created in reponse to the question "What is the difference between pki/scripts and pki/base/scripts?"
This was the answer provided:
We used to have similar directories (e. g. - 'pki/dogtag/scripts' and 'pki/redhat/scripts' associated with the Dogtag and Red Hat themes respectively) which housed scripts primarily used for the legacy method of building individual RPMS and SRPMS (e. g. - pki-ca RPM and pki-ca SRPM as opposed to pki-ca RPM and pki-core SRPM). This separation allowed theme packages and their icons to reside in separate repositories and still be built utilizing the same core server/client pieces, as at that time, at least one theme was required and the themes were mutually exclusive.
Since we do not really ship any devel packages, the scripts under 'pki/base/scripts' were just meant for un-packaged development tools related to the core server/client pieces - similar to the 'pki/tools' directory which was created at a later date to house development tools which were not scripts.
Since Dogtag 10.x builds individual SRPMS which often contain numerous RPMS, the 'pki/scripts/' directory houses scripts used for building these and pertain to the PKI project as well as its default Dogtag theme.
It may make sense to re-organize and consolidate some of these directories.