Diego 'Flameeyes' Pettenò wrote: >Currently pam stuff (implementations, modules) are organized in the worst way >I ever seen. >Most of them are in sys-libs, some of them in app-admin, other in app-crypt, >pam_smb in net-misc and so on. > >I think we should reorganize them and have a sys-pam category with >implementations (Linux-PAM and OpenPAM) and the modules needed. > >Such a change would require a lot of work and we can't count on epkgmove I >think, but if someone is going to help me or at least tell me how to do such >a change without breaking everything (always if such a change is accepted, >obv.).. > >Comments? > > here is how I do package moves: - first I search all tree to see which packages depends on the package I wanna move - copy src -> dst and erase CVS dirs from dst - cvs add dst dst/files - cvs add all_files - search and replace the old name with the new name (usually you should edit only the first line of the ChangeLog) - add a comment in ChangeLog - repoman commit dst - put a record in /profiles/updates/?Q-200? - cvs delete all_files_from src - cvs commit src - replace & repoman commit dependencies found at first step
it is a laborious work, but it could be done. too bad we don't use subversion :(
signature.asc
Description: OpenPGP digital signature
