صفحهٔ اصلی گشت‌و‌گذار راهنما
ورود
thomassgn
/
guixsd-configuration
دنبال کردن 2
ستاره دار 3
انشعاب 0
پرونده‌ها مشکلات 0 درخواست واکشی 0 ویکی
شاخه: master
شاخه‌ها تگ‌ها
guixsd-confi...
/
README

README 10 KB
لینک دائمی تاريخچه خام

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162 
  1. # GuixSD Configuration \
    2. 

  2.   for merlin.browniehive.net
    3. 

  3. 

  4. Be aware of silly commit messages. Also, be aware that notabug removes strings inside angle brackets '<' so names from the irc log is snipped out, but they are there... :P
    5. 

  5. 

  6. # TODO
    7. 

  7. 

  8. SHEPHERD SERVICES!
    9. 

  9. 

  10. - Mcron: check and fix missing /var/run/tor. And check for battery - launch i3nagbar.
    11. 

  11. - [DONE-ish] Fix battery alert using i3-nagbar. Y U NO Do wat I want?
    12. 

  12. 

  13. - rottlog? logrot?
    14. 

  14. - Check and look through others/pkill9-desktop-config.scm
    15. 

  15. - Send patch for norwegian dict
    16. 

  16. - change or fix "build system" Now is a disaster of manual operations and failing scripts.
    17. 

  17. - linode;
    18. 

  18. - gvfs/fuser for usb and mmc;
    19. 

  19. - wkhtmltopdf(.org)
    20. 

  20. - BORG BACKUP: Almost done, need somewhere to backup to.
    21. 

  21. - VPN: merlin - linode - quercus
    22. 

  22. - WWOFFLE? https://www.gedanken.org.uk/software/wwwoffle/README
    23. 

  23. - fetchmail?
    24. 

  24. 

  25. # brhive
    26. 

  26. 

  27. - Check ./maintenance/hydra/berlin.scm and so on as servers
    28. 

  28. - Check ./others/ng0-old-systems/guixsd/servers/{shadownet,mailserver,++}
    29. 

  29. - Migrate to guixsd.
    30. 

  30. - evaluate alternatives for linode
    31. 

  31. - ?setup weeslack?: https://github.com/wee-slack/wee-slack
    32. 

  32. - ipfs?
    33. 

  33. - xmpp
    34. 

  34. - ¿mail?
    35. 

  35. - httpd
    36. 

  36. - vpn!
    37. 

  37. - mosh
    38. 

  38. - whatever else is on linode now
    39. 

  39. - Setup quercus! even though physical location is undecided atm.
    40. 

  40. 

  41. ## Hitpoints is dead
    42. 

  42. 

  43. Got our hands on a macbook, now called merlin.
    44. 

  44. Look at the following for setup:
    45. 

  45. https://medium.com/@philpl/arch-linux-running-on-my-macbook-2ea525ebefe3
    46. 

  46. http://www.frankshin.com/macbook-air-62-2013-setting-it-up-with-archlinux/
    47. 

  47. https://github.com/pandeiro/arch-on-air
    48. 

  48. 

  49. # Notes
    50. 

  50. 

  51. ## This is on inheritance (is this inheritance from guix or guile?) from the #guix IRC channel:
    52. 

  52. 

  53. [16:29:19]	<thomassgn>	snape: allright, that does the trick. quite cumbersome though, it keeps throwing these at me, resolving number 3 now... :)
    54. 

  54. [16:29:32]	* marusich has quit (Quit: Leaving)
    55. 

  55. [16:30:08]	<snape>	thomassgn: as an alternative, you can just run "guix build <my-package>" in a shell
    56. 

  56. [16:34:10]	<thomassgn>	hehe, yes. Or not really. 'guix build -f ./libreoffice.scm libreoffice' tells me it cannot build. how can I tell it to build this definition of package...?
    57. 

  57. [16:34:50]	<snape>	you need to put it into GUIX_PACKAGE_PATH
    58. 

  58. [16:35:36]	<snape>	thomassgn: see https://www.gnu.org/software/guix/manual/guix.html#Defining-Packages
    59. 

  59. [16:35:50]	<snape>	if it's your own package file
    60. 

  60. [16:36:06]	<snape>	if it's within the guix source, then guix build libreoffice should work
    61. 

  61. [16:36:44]	<thomassgn>	ok. But how do I know which libreoffice it builds if I say guix package -i libreoffice? I'm just testing a few things, and would like to do just copy the file and test some changes...
    62. 

  62. [16:37:16]	<thomassgn>	I guess I could start changing the names and so on in the package definition.
    63. 

  63. [16:37:17]	<snape>	if you modify Guix's libreoffice definition and run: "guix build libreoffice", it will build the modified libreoffice
    64. 

  64. [16:37:39]	<thomassgn>	but I'm not modifying in place
    65. 

  65. [16:38:01]	<efraim>	GUIX_PACKAGE_PATH takes precedence over guix proper for leaf packages
    66. 

  66. [16:38:16]	<thomassgn>	cause it's read only in my profile... :)
    67. 

  67. [16:38:19]	<thomassgn>	Ah!
    68. 

  68. [16:38:44]	<snape>	thomassgn: your custom libreoffice package should probably inherit Guix's one
    69. 

  69. [16:39:17]	* atw has joined #guix
    70. 

  70. [16:39:18]	<snape>	so that you don't have to copy everything
    71. 

  71. [16:39:23]	<thomassgn>	nice. So any package with duplicate variable-name in my GUIX_PACKAGE_PATH will always be chosen?! nice.
    72. 

  72. [16:39:39]	<snape>	yes, but it's probably clearer if the name is different
    73. 

  73. [16:39:52]	<snape>	say, my-libreoffice
    74. 

  74. [16:39:52]	<thomassgn>	Yes, I don't entirely understand inheritance though :P I'm a bit slow :)
    75. 

  75. [16:40:16]	<snape>	you're not slow, it takes time ;)
    76. 

  76. [16:41:50]	<snape>	thomassgn: there are a few package inheritance examples in the Guix source. You can grep "inherit" in /gnu/packages/ to see them.
    77. 

  77. [16:42:45]	<thomassgn>	cool, I'll have a look. I've used it once in a simple thing I mostly copied.
    78. 

  78. [16:43:05]	<snape>	also, things in GUIX_PACKAGE_PATH need to be valid Guile modules
    79. 

  79. [16:43:46]	<rekado>	inheritance is a way to avoid duplication.
    80. 

  80. [16:43:46]	<resh>	https://thepasteb.in/p/76hE6RvkK2DHV
    81. 

  81. [16:44:03]	<thomassgn>	hehe, yes. I keep getting warnings from guix commands when I'm fiddling with somethings in there.
    82. 

  82. [16:44:05]	<rekado>	a package can inherit all fields from another package.
    83. 

  83. [16:44:19]	<rekado>	you can then override individual fields without having to specify others.
    84. 

  84. [16:44:23]	* atw has quit (Ping timeout: 260 seconds)
    85. 

  85. [16:44:46]	<roptat>	resh: is the tarball in /tmp?
    86. 

  86. [16:44:46]	<rekado>	resh: where is the tar.xz file?
    87. 

  87. [16:45:07]	<thomassgn>	ah, but if I specify parts of a field will it append it to contents of the previous? or discard the previous?
    88. 

  88. [16:45:15]	<thomassgn>	previous=inherited
    89. 

  89. [16:45:24]	<roptat>	discard
    90. 

  90. [16:45:27]	<thomassgn>	right
    91. 

  91. [16:45:56]	<roptat>	but you can get the value by using (package-<field-name> libreoffice)
    92. 

  92. [16:46:14]	<resh>	roptat and rekado not inside any directory ... installed without cd to any directory
    93. 

  93. [16:47:03]	<rekado>	resh: so it might still be in your home directory then.
    94. 

  94. [16:47:08]	<thomassgn>	So if I just want to add something I have to copy the contents of the inherited field into the new def.? uh, sorry, what did you mean with (package-<field-name> libreoffice)? I ould just go read the docs ofc.
    95. 

  95. [16:47:25]	<thomassgn>	roptat: ^^
    96. 

  96. [16:47:39]	<rekado>	thomassgn: (package-synopsis libreoffice) gives you the synopsis of the libreoffice package, for example.
    97. 

  97. [16:47:51]	<rekado>	thomassgn: (package-inputs libreoffice) gives you the inputs.
    98. 

  98. [16:47:59]	<roptat>	for instance to add an input you would write (inputs `(("some-package" ,some-package) ,@(package-inputs libreoffice)))
    99. 

  99. [16:48:18]	<roptat>	with enough parenthesis
    100. 

  100. [16:48:48]	<thomassgn>	haha, Nice. Thanks :)
    101. 

  101. [16:49:08]	<rekado>	i.e. the inputs field has a quasi-quoted list with the list ("some-package" ,some-package) followed by the items in the inputs field of the libreoffice package.
    102. 

  102. 

  103. 

  104. ## And from guix mailing list about environments "permanence":
    105. 

  105. 

  106. > Hello, I've been using guix `environment -l env.scm` to work on
    107. 

  107. > different programming projects on my laptop.
    108. 

  108. > The problem is: When I do guix pull or gc, these environments might get
    109. 

  109. > lost, and when I'm on the train with no network and run `guix
    110. 

  110. > environment` it will try to graft/rebuild/whatever, which requires an
    111. 

  111. > internet connection, instead of just opening the last working environment.
    112. 

  112. > So I can't work on my projects until I get back online.  
    113. 

  113. 

  114. To protect your environment from GC, you can use ‘guix environment
    115. 

  115. --root’: it register a “garbage collector root” for your environment as
    116. 

  116. a symlink, which means your environment won’t be GC’d unless you remove
    117. 

  117. that symlink.
    118. 

  118. 

  119. To prevent your environment from being updated even if you ran ‘guix
    120. 

  120. pull’ in the meantime, you can use a separate profile.  For instance,
    121. 

  121. you can create a ‘dev’ profile for your development environment:
    122. 

  122. 

  123.   guix package -p dev -i gcc-toolchain make
    124. 

  124. 

  125. and then whenever you want to “enter” that profile, do:
    126. 

  126. 

  127.   . ./dev/etc/profile
    128. 

  128. 

  129. And of course you can have as many profiles as you want.
    130. 

  130. 

  131. ## And from IRC on commit messages, emacs and yasnippets
    132. 

  132. 

  133. [09:44:52]	<thomassgn>	Hey, I've been fixing the package definitions I sent in the other day. I'm writing the commitmessage now, but after reading the gnu changelog standards I have a few questions: My current commit message looks like "* gnu/packages/xdisorg.scm (screen-message): Add package definition" Should I add more explanation? and from before I'm used to putting just 68 characters on the first line no punctuation and then
    134. 

  134. [09:44:54]	<thomassgn>	blank line before any more descritpion, but the gnu standards seem to say differently. is that right?
    135. 

  135. [09:47:45]	<roptat>	thomassgn: it should be "* gnu/packages/xdisorg.scm (screen-message): New variable."
    136. 

  136. [09:47:57]	<roptat>	see other commit messages for examples
    137. 

  137. [09:48:43]	<thomassgn>	roptat: ah, I've tried looking at other commits and can't see any adding packages. I'm doing something wrong, yes.
    138. 

  138. [09:49:12]	<rekado>	I want to build “axoloti-patcher” but the patch for “axoloti-libusb” no longer applies. So I updated the patch, but Guix still insists on applying the old version of the patch.
    139. 

  139. [09:49:19]	<rekado>	What am I doing wrong?
    140. 

  140. [10:09:07]	<roptat>	thomassgn: I think I confused you: the message should be "gnu: Add screen-message", a blank line and then "* gnu/packages/xdisorg.scm (screen-message): New variable.""
    141. 

  141. [10:09:47]	<roptat>	and don't sign-off your own patch
    142. 

  142. [10:09:52]	<snape>	with a '.' after "Add screen-message" :-)
    143. 

  143. [10:16:20]	<thomassgn>	derp. ok, sent them allready. these guidelines are too complex/confusing for me it seems.
    144. 

  144. [10:16:54]	<thomassgn>	thanks for pointing it out though, next commit message will be a bit better.
    145. 

  145. [10:18:06]	<rekado>	thomassgn: if you’re using Emacs + magit you may find our commit message snippets useful.
    146. 

  146. [10:18:22]	<rekado>	they are in etc/snippets and can be used with yasnippet.
    147. 

  147. [10:18:57]	<rekado>	I only type “add” hit TAB and it expands to the right text for adding a new package.
    148. 

  148. [10:18:57]	<thomassgn>	rekado: cool, is there an easy way to add them? Ah, yasnippet: the plugin I've had since the start, but never used... :P
    149. 

  149. [10:19:07]	<thomassgn>	awesome
    150. 

  150. [10:19:24]	<rekado>	thomassgn: take a look at the contributing manual section.
    151. 

  151. [10:19:36]	<rekado>	it tells you how to set this up.
    152. 

  152. [10:22:32]	<thomassgn>	you mean the section "the perfect setup"?
    153. 

  153. [10:22:57]	<rekado>	yes, that’s the one
    154. 

  154. [10:23:43]	<rekado>	BTW my patch problem was due to GUIX_PACKAGE_PATH, which included a duplicate package definition
    155. 

  155. [10:23:44]	<thomassgn>	cause it assumes that I'm working in a git checkout of the guix source, which I don't. I remember I couldn't make it work, too much confusion between my running system and the git checkout...
    156. 

  156. [10:24:21]	<rekado>	you can also just copy the snippets to some other directory and refer to them.
    157. 

  157. [10:24:32]	<rekado>	you don’t need to wrok from a git checkout to use the snippets.
    158. 

  158. [10:24:45]	<rekado>	(but I do wonder how you submit patches when you don’t use a git checkout.)
    159. 

  159. [10:25:08]	<thomassgn>	I understand a lot more now, compared to last time I tried this. So I'll probably try again soon.
    160. 

  160. [10:27:01]	<wigust>	thomassgn: Also “C-x v l runs the command vc-print-log” in file you want to commit helps with a commit message.
    161. 

  161. [10:27:09]	<thomassgn>	oh I do use git, but I have my own repo where I write and test package defs. and then I copy the defs over to the guix src checkout and make the patch. Yes it's tedious, but I understand what's happening and I don't have errors I don't understand flowing around... :P
    162. 

  162. [10:27:46]	<thomassgn>	cool, thanks wigust and rekado
    163.