From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Moving packages to dev-vcs
Date: Thu, 4 Mar 2010 23:28:55 +0200 [thread overview]
Message-ID: <201003042329.01209.hwoarang@gentoo.org> (raw)
In-Reply-To: <4B902136.8090106@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 1376 bytes --]
On Thursday 04 March 2010 23:08:06 Sebastian Pipping wrote:
> Hello!
>
>
> So now that we have a new category "dev-vcs" we need to move suitable
> stuff over there. Moving packages is complex and error prone:
> This mail tries to guide you through and summarize the process, please
> read on.
>
> HINT: Please keep CVS' radius of operation small to reduce risks.
>
>
> 0. Prepare
> ==========
> - Check if your package fits:
> Is it a "utility focused on version control"?
>
> - Ensure that you have permission (if you are not the main maintainer)
>
> - Sync the whole tree including profiles
> (as you'll be inspecting reverse dependencies)
>
>
> 1. Copy
> =======
> - Duplicate any traces of dev-util/${PN} in profiles/ to dev-vcs/${PN}
> (fgrep -Rw "dev-util/${PN}" profiles/)
>
> - Copy complete package dev-util/${PN} to dev-vcs/${PN}
> (watch out CVS directories)
>
>
> 2. Switch
> =========
> - Update eclasses
> fgrep -w "dev-util/${PN}" eclass/*.eclass
>
> - Update reverse dependencies
> http://tinderbox.dev.gentoo.org/misc/dindex/dev-util/${PN}
> http://tinderbox.dev.gentoo.org/misc/rindex/dev-util/${PN}
This might require too much time so the tree will be broken for a while I
guess
--
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-03-04 21:30 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 21:08 [gentoo-dev] Moving packages to dev-vcs Sebastian Pipping
2010-03-04 21:21 ` Ulrich Mueller
2010-03-04 21:28 ` Markos Chandras [this message]
2010-03-05 5:51 ` Petteri Räty
2010-03-04 21:38 ` Robin H. Johnson
2010-03-04 21:40 ` Dirkjan Ochtman
2010-03-05 0:31 ` Sebastian Pipping
2010-03-17 18:08 ` Sebastian Pipping
2010-03-04 22:11 ` Brian Harring
2010-03-05 20:18 ` Sebastian Pipping
2010-03-05 3:17 ` [gentoo-dev] " Ryan Hill
2010-03-05 4:57 ` [gentoo-dev] " Serkan Kaba
2010-03-05 9:22 ` [gentoo-dev] " Christian Faulhammer
2010-03-05 13:32 ` Serkan Kaba
2010-03-05 17:10 ` [gentoo-dev] " Jeroen Roovers
2010-03-05 17:18 ` Sebastian Pipping
2010-03-06 7:08 ` Petteri Räty
2010-03-07 4:44 ` Sebastian Pipping
2010-03-08 18:58 ` Fabian Groffen
2010-03-15 19:50 ` Sebastian Pipping
2010-03-15 20:02 ` 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=201003042329.01209.hwoarang@gentoo.org \
--to=hwoarang@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