-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/07/2015 05:56 AM, Jauhien Piatlicki wrote: > Hi, > > On 09/07/2015 07:28 AM, Daniel Campbell wrote: >> On 09/06/2015 02:00 PM, Jauhien Piatlicki wrote: >>> Hi, >> >>> On 09/05/2015 11:23 PM, Daniel Campbell wrote: >>>> On 09/05/2015 01:04 PM, Matthew Thode wrote: >> >>>>> I think cargo should probably go in dev-util with other >>>>> rust libraries and programs going into dev-rust as needed, >>>>> but that's just me :D >>>> >>>> Agreed. dev-util until it grows in size (isn't the >>>> recommendation 5-10+ pkgs?), then dev-rust. Despite the >>>> package moves being somewhat cumbersome, it makes more sense >>>> to do it once it's clear Rust has an ecosystem going rather >>>> than catch stragglers in its infancy. >>>> >> >>> Ok, looks quite logical for me. So the next question. I >>> remember portage had some problems with moving packages. Would >>> it work if I'll move dev-rust/cargo to dev-util/cargo in our >>> overlay now. And later when rust infrastructure grows move it >>> in the main tree back to dev-rust? Or will it break something? >> >>> -- Jauhien >> >> >> Now that we're on git, I don't see why a quick `git mv >> old-cat/foo new-cat/foo` wouldn't get the job done. Don't quote >> me on it, but my guess is it would work fine. Then make sure the >> profile data gets updated by updating the relevant file(s). >> >> If you're keeping it in an overlay until you think it's ready for >> the Gentoo repo, you may as well keep it whatever you want since >> it's not bound by Gentoo policy. I would start with dev-util, >> even in tree, and migrate to dev-rust when it reaches critical >> mass on packages (I'd say at least ten). >> >> > > I'm speaking not about git, but about portage move [1] (see Moving > ebuilds there). This is unrelated to version control. > > [1] https://devmanual.gentoo.org/ebuild-maintenance/index.html > Right, that's what the 'updating the relevant file(s)' part was about. :) If you're the only developer working on it, I don't see why it would be a problem. Of course, other developers who are more experienced in these situations should probably show up and say something, but based on what you've told me and the processes Gentoo has in place, it should be okay.
- -- Daniel Campbell - Gentoo Developer OpenPGP Key: 0x1EA055D6 @ hkp://keys.gnupg.net fpr: AE03 9064 AE00 053C 270C 1DE4 6F7A 9091 1EA0 55D6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJV7bGLAAoJEAEkDpRQOeFwpJgQANOst5gnRN5fwETnrR42bQYD aqZn4+ZAF8tHN45XUsa9RzCY1w9YO1GBxUPhkhUBIesJPB326gy8pc9TL/g2VNfF QcWEfh0loiqE5pAE1IjAeLROR01AEfADIivoBKJ2kTr2ziztxxjIab30UY1WfaxX kvXY5bEi9AQPW28e4cdNBX8JBJqn+V31allS+AnVZApd6+FPU/UfjZ5TF9JC9w04 qS6gd0fRBWXSb8cZoufJkgiDttlleSW89AxYJKTOAUCDO8opfVr/kPB5UY22Jftd LdXl/5U0jAlt5OEthSZvDBB6cJ0ydI5DmtjMG93DXQcxXTfMneI45H6UAw0SXdt6 Ss/Uy2fHLojSP07rcWhUt7RNaXNUhEbhnplu4Gf8iHRymPIbUTS8MaM37nCDvouV GE2puyUFvn11l14JIcJLKT4zfEd9+9pM2m8IhrCjF86c4KRfUXJsQzZmavmAcUiY Fn7oMv4/WaQa+V4y6fQzpedBBoeGNpxmunOYOKvlx2puwd3UJGOn6szCL4vLKQW8 dxuNIiTSc1aIUHKoaIKqeZ4fwNQFcAhnxuoyd5Z4zZ1zKE5VFVBCAV+gadzH3w2K x40my64c4KxUy+1gKB6yvXAU3KP5HqIuoM9dcUJqLmoWgyzWk9gO5k2P30IKABdM 74Ks5PKTyvNF5T8hxpt/ =I0es -----END PGP SIGNATURE-----
