Gentoo Archives: gentoo-dev

From: NP-Hardass <NP-Hardass@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] symlinks in the tree
Date: Sun, 13 Sep 2015 03:50:51
Message-Id: 20150912235024.334797e5@Valar-Morghulis.home.adambfeldman.com
In Reply to: [gentoo-dev] symlinks in the tree by "Justin Lecher (jlec)"
1 -----BEGIN PGP SIGNED MESSAGE-----
2 Hash: SHA256
3
4 In my wine-a-holics overlay, I used symlinks. I found that
5 occassionally, git would act up and replace the symlink with the linked
6 file when committing. I never found out how or why, but for this
7 reason alone, I highly recommend against it.
8
9 Regarding the comment about regular and live versions, I'd also
10 recommend against this for the simple reason that sometimes something
11 changes upstream before a release comes out, and it adds an additional
12 complication of worrying about edits to the live version changing a
13 versioned ebuild.
14
15 - --NP-Hardass
16
17 On Sat, 12 Sep 2015 15:12:08 +0200
18 "Justin Lecher (jlec)" <jlec@g.o> wrote:
19
20 > -----BEGIN PGP SIGNED MESSAGE-----
21 > Hash: SHA512
22 >
23 > Hi,
24 >
25 > I would like to discuss the pro and cons of usage of symlinks in the
26 > tree, which are possible now as we aren't bound to CVS anymore
27 >
28 > We have quite a number of ebuilds already in the tree defining
29 > functionality for both, regular version and live versions. These are
30 > typical candidates. Same for different package versions with the same
31 > ebuild.
32 >
33 > What is your opinion on making heavy use of symlinks here?
34 >
35 > Personally I would ban symlinks and duplicated code. One ebuild for
36 > one version. And in case you like to propagate changes over several
37 > ebuilds, just use tools like meld.
38 >
39 > A drawback is that tools like sed break symlinks and write back a
40 > plain files.
41 >
42 > And last, we have potential breakages if people don't give enough care
43 > when doing stabilizations and removal of version.
44 >
45 > nevertheless, we would slim the tree and reduce work when changing
46 > things like HOMEPAGE.
47 >
48 > So please discuss this matter.
49 >
50 > Justin
51 > -----BEGIN PGP SIGNATURE-----
52 > Version: GnuPG/MacGPG2 v2.0
53 >
54 > iQJ8BAEBCgBmBQJV9CSoXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
55 > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF
56 > OTQwMkE3OUIwMzUyOUEyAAoJEOlAKnmwNSmiIZ0P/0q6jSuGZzZ4lDiu87GIYMiC
57 > ndRzHsR/OGT9paB01pkoQogOt9+AMKdNd434n2to+HbuNf7Le5cWP7MBAdD/ydzV
58 > H+5zE98Mu9h8IXTRvuxv6eTSRPFsnnDPuMAS+28D7WwDBcmOhl4we/hRyfq0+JFw
59 > s5XojNlrk7YZLynZs8SHcgqq5CbaKbjLMsVSTnVXKeA1NcaB0lPFjI0JraCqW4xS
60 > BgIA2MrrR5XM2imvmBInanwJZ+VOVvHD1jxTlfUQeF7qJusTY5fTnVncvnIo72Fh
61 > E2Rz/+vrWFe+CvQV63IpgbtC2oYP5OMidnfZSQynRbGsK9w3rm25cXOlyXjLA98O
62 > sv/wNHvVk3+SIvIviN3yDjOOG5q1zeW33UtZfz5iKu3E7dUGw6B2a/qjC9m9lIQH
63 > GGDu7csYnW8aSLiEJPGsJsduTqw/+G5p8DWMGuHss6xu6DyZKJPRxgd4VlDkLIiE
64 > ZCgoHCGhQX3LDEOlzh7+j01A1AOO4SfTZqqDch8f6jiLYmx0dw4Rcz6Lth+cAzn+
65 > fjTdq8A1P5umV8NiwGZtx8GtPoEWRpEV0zuhZHWXjvFSIxpn2TBUi+pETo421wXH
66 > 9QDQD5Q/9Wf/Wckyb86+OEhwBGoPXib2sF1BOTWONXHECvQ5xuqXy2Ux34HJHbou
67 > Que3NfC4OiQKXSJv1jae
68 > =K93a
69 > -----END PGP SIGNATURE-----
70 >
71
72 -----BEGIN PGP SIGNATURE-----
73 Version: GnuPG v2
74
75 iQIcBAEBCAAGBQJV9PKMAAoJEBzZQR2yrxj7498P/3ITnQ3Ji8MaPGbv3AWK52SN
76 hccXU3Bjyq7I/A+1H/ZYzmBRtLkANczeCcqOBQTIr2p7s3lFfnvRVAfrpyRsmo1s
77 ix9Pmf/9ixDZ+dHUxliARiYNZHWNtisxCF5ehmo8+q/F5efLslrjKNf81X9xDpaL
78 Haz5ywWUfVRXWZwWjgc5dSLfqauPYZSE9B3NzOgjKnRT9OeYT/5dMHf6rgkPi2jT
79 O2NeYI2zKL93hspxM4ot1QBhlmKAw2ArjDMoV5UkjpvKa/4FKXu8h34dgwZH0AYJ
80 2WlIMXREUt1iR+FYQ+hUEzOsEO7HgSlz7wfn0Z7SJUFObhXTzIlMLjm5wbVbjsVx
81 rzz/XEXJlU8OFjy5h2MfoFWn0I46ysgFtie7OaRl/Rq3jqLg6irLAmwgiqJbLgCa
82 qcwUt3EhbWqSr5NlHdxCHfjnOwYsTrd+cX0FEhMNW2pFO8oBXa4Xz+x4PiZAz07M
83 RyRftQucd2JbY+TE2nS51HzJYN8157ZkPJ1SnNN38Nftd0oD0XJ9UmeYhO45Gc6W
84 wRpX75af1dUhgs3nh6CpnYCXuWe8Aa08vf2WWTpw72QdcurI3cSrYcjScDXbF4Yw
85 hthsaaP+rwDCFacFdY24Rglg01Q45mWq23mylVwnmMUtG3qvE0Nhu3ZIBtqx+j5O
86 gsujfaXNV5U/jsnCWDMf
87 =8n1u
88 -----END PGP SIGNATURE-----