-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 In my wine-a-holics overlay, I used symlinks. I found that occassionally, git would act up and replace the symlink with the linked file when committing. I never found out how or why, but for this reason alone, I highly recommend against it.
Regarding the comment about regular and live versions, I'd also recommend against this for the simple reason that sometimes something changes upstream before a release comes out, and it adds an additional complication of worrying about edits to the live version changing a versioned ebuild. - --NP-Hardass On Sat, 12 Sep 2015 15:12:08 +0200 "Justin Lecher (jlec)" <j...@gentoo.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Hi, > > I would like to discuss the pro and cons of usage of symlinks in the > tree, which are possible now as we aren't bound to CVS anymore > > We have quite a number of ebuilds already in the tree defining > functionality for both, regular version and live versions. These are > typical candidates. Same for different package versions with the same > ebuild. > > What is your opinion on making heavy use of symlinks here? > > Personally I would ban symlinks and duplicated code. One ebuild for > one version. And in case you like to propagate changes over several > ebuilds, just use tools like meld. > > A drawback is that tools like sed break symlinks and write back a > plain files. > > And last, we have potential breakages if people don't give enough care > when doing stabilizations and removal of version. > > nevertheless, we would slim the tree and reduce work when changing > things like HOMEPAGE. > > So please discuss this matter. > > Justin > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0 > > iQJ8BAEBCgBmBQJV9CSoXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w > ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ0QUU0N0I4NzFERUI0MTJFN0EyODE0NUFF > OTQwMkE3OUIwMzUyOUEyAAoJEOlAKnmwNSmiIZ0P/0q6jSuGZzZ4lDiu87GIYMiC > ndRzHsR/OGT9paB01pkoQogOt9+AMKdNd434n2to+HbuNf7Le5cWP7MBAdD/ydzV > H+5zE98Mu9h8IXTRvuxv6eTSRPFsnnDPuMAS+28D7WwDBcmOhl4we/hRyfq0+JFw > s5XojNlrk7YZLynZs8SHcgqq5CbaKbjLMsVSTnVXKeA1NcaB0lPFjI0JraCqW4xS > BgIA2MrrR5XM2imvmBInanwJZ+VOVvHD1jxTlfUQeF7qJusTY5fTnVncvnIo72Fh > E2Rz/+vrWFe+CvQV63IpgbtC2oYP5OMidnfZSQynRbGsK9w3rm25cXOlyXjLA98O > sv/wNHvVk3+SIvIviN3yDjOOG5q1zeW33UtZfz5iKu3E7dUGw6B2a/qjC9m9lIQH > GGDu7csYnW8aSLiEJPGsJsduTqw/+G5p8DWMGuHss6xu6DyZKJPRxgd4VlDkLIiE > ZCgoHCGhQX3LDEOlzh7+j01A1AOO4SfTZqqDch8f6jiLYmx0dw4Rcz6Lth+cAzn+ > fjTdq8A1P5umV8NiwGZtx8GtPoEWRpEV0zuhZHWXjvFSIxpn2TBUi+pETo421wXH > 9QDQD5Q/9Wf/Wckyb86+OEhwBGoPXib2sF1BOTWONXHECvQ5xuqXy2Ux34HJHbou > Que3NfC4OiQKXSJv1jae > =K93a > -----END PGP SIGNATURE----- > -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJV9PKMAAoJEBzZQR2yrxj7498P/3ITnQ3Ji8MaPGbv3AWK52SN hccXU3Bjyq7I/A+1H/ZYzmBRtLkANczeCcqOBQTIr2p7s3lFfnvRVAfrpyRsmo1s ix9Pmf/9ixDZ+dHUxliARiYNZHWNtisxCF5ehmo8+q/F5efLslrjKNf81X9xDpaL Haz5ywWUfVRXWZwWjgc5dSLfqauPYZSE9B3NzOgjKnRT9OeYT/5dMHf6rgkPi2jT O2NeYI2zKL93hspxM4ot1QBhlmKAw2ArjDMoV5UkjpvKa/4FKXu8h34dgwZH0AYJ 2WlIMXREUt1iR+FYQ+hUEzOsEO7HgSlz7wfn0Z7SJUFObhXTzIlMLjm5wbVbjsVx rzz/XEXJlU8OFjy5h2MfoFWn0I46ysgFtie7OaRl/Rq3jqLg6irLAmwgiqJbLgCa qcwUt3EhbWqSr5NlHdxCHfjnOwYsTrd+cX0FEhMNW2pFO8oBXa4Xz+x4PiZAz07M RyRftQucd2JbY+TE2nS51HzJYN8157ZkPJ1SnNN38Nftd0oD0XJ9UmeYhO45Gc6W wRpX75af1dUhgs3nh6CpnYCXuWe8Aa08vf2WWTpw72QdcurI3cSrYcjScDXbF4Yw hthsaaP+rwDCFacFdY24Rglg01Q45mWq23mylVwnmMUtG3qvE0Nhu3ZIBtqx+j5O gsujfaXNV5U/jsnCWDMf =8n1u -----END PGP SIGNATURE-----
