| 3 Dec 2023 |
|  GitBot [git] changed their display name from GitBot#8618 to GitBot [git]. | 14:02:50 |
|  darkevilpt joined the room. | 15:27:27 |
| 4 Dec 2023 |
|  manan__kataria joined the room. | 11:41:25 |
| 7 Dec 2023 |
|  _sayde_ changed their display name from queen_astraa to _sayde_. | 04:31:28 |
|  d3sox changed their display name from d3sox#0 to d3sox. | 08:23:05 |
|  databoosee_55130 joined the room. | 17:26:36 |
| 8 Dec 2023 |
|  iconoclasthero joined the room. | 21:04:06 |
| 9 Dec 2023 |
 moonstruck6866 | ive got a question about pacscript best practice | 06:17:03 |
| moonstruck6866 | Ive got an open source cross platform chemistry app that comes in an appimage
it has plugins/extensions
several of them are default on windows/mac, but the appimage doesnt have them
this straight up breaks the software, many of the features are unusable because they rely on these plugins that have been grandfathered into the default install, but are still labeled as "extensions" because they use external softwere | 06:19:48 |
| moonstruck6866 | these default extensions still have versioning, though | 06:20:39 |
| moonstruck6866 | do I make a pacscript for every extension?
do I wrap them all into one?
whats the play here? | 06:21:35 |
 MEE6 [!] | GG moonstruck6866, you just advanced to level 1! | 06:21:35 |
 Elsie | give the link to the software | 14:33:45 |
|  .dismissed. | 14:38:48 |
| .dismissed. | 14:39:21 |
| moonstruck6866 | https://www.openchemistry.org/projects/avogadro2/
AppImage:
also requires fuse3, they didnt package that in for some ass reason
https://github.com/OpenChemistry/avogadrolibs/releases/download/1.98.1/Avogadro2-x86_64.AppImage | 15:01:29 |
| Elsie | does it offer non-appimage stuff? | 15:02:05 |
| moonstruck6866 | https://github.com/OpenChemistry/avogadroapp/releases/tag/1.98.1 | 15:03:25 |
| moonstruck6866 | you can build from source | 15:03:27 |
| Elsie | let's do that | 15:03:43 |
| moonstruck6866 | build bins i assume? or something else? | 15:06:18 |
| moonstruck6866 | also, what should i do about the plugins and their versioning?
do pacscripts allow custom variables in the pacscripts just for convience that arent read by pacstall? | 15:08:06 |
| Elsie | yes | 15:08:21 |
| Elsie | check out emacs and emacs-git for exmaples | 15:08:27 |
| Elsie | * check out emacs and emacs-git for examples | 15:08:30 |
| moonstruck6866 | awesome | 15:08:41 |
| moonstruck6866 | oh wait are you meaning having the pacscript instruct them to build it from source, downloading the source code | 15:18:56 |
| Elsie | well, can you compile plugins in? | 15:19:28 |
| moonstruck6866 | im honestly not sure, I was planning on doing it after the fact, linking to each plugin | 15:20:10 |
| moonstruck6866 | im not sure about putting the plugins in before building | 15:20:34 |
