public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alin Nastac <mrness@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Proposal: sys-pam category
Date: Sun, 05 Jun 2005 17:44:51 +0300	[thread overview]
Message-ID: <42A30FE3.10100@gentoo.org> (raw)
In-Reply-To: <200506051622.24240@enterprise.flameeyes.is-a-geek.org>

[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]

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 :(


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2005-06-05 14:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-05 14:22 [gentoo-dev] Proposal: sys-pam category Diego 'Flameeyes' Pettenò
2005-06-05 14:44 ` Alin Nastac [this message]
2005-06-06  0:34   ` Mike Doty
2005-06-06  4:00     ` Alin Nastac
2005-06-05 15:37 ` Ned Ludd
2005-06-05 16:34   ` Jonas Geiregat
2005-06-05 16:42     ` foser
2005-06-05 17:25       ` Nathan L. Adams
2005-06-05 18:13         ` Ned Ludd
2005-06-05 20:57           ` Nathan L. Adams
2005-06-05 21:03             ` Nathan L. Adams
2005-06-05 21:55             ` Ned Ludd
2005-06-06 10:43               ` Jan Jitse Venselaar
2005-06-05 19:13         ` Jonas Geiregat
2005-06-05 17:34   ` Diego 'Flameeyes' Pettenò
2005-06-05 19:03     ` Ned Ludd
2005-06-05 19:21       ` Diego 'Flameeyes' Pettenò
2005-06-05 20:13         ` Ned Ludd
2005-06-06 19:47         ` Kevin F. Quinn
2005-06-05 17:50   ` Michael Cummings
2005-06-05 18:10     ` Lance Albertson
2005-06-06 14:06     ` [gentoo-dev] " sf
2005-06-06 14:29       ` Jason Stubbs
2005-06-05 15:59 ` [gentoo-dev] " Ian Leitch
2005-06-05 22:03 ` Robin H. Johnson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=42A30FE3.10100@gentoo.org \
    --to=mrness@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox