discourse extension has a wrong dependency

[choroba]

At https://ufal.mff.cuni.cz/tred/extensions, discourse depends on nondeprel_common, but it's location is incorrectly referred to as external (should be core).

In the repository, the path is correct, but the version is 1.149, while the one ufal is 1.157. Where is it coming from and could it be fixed there (and probably removed from here)?

[jmirovsky]

Going to move discourse, bridging and nondeprel_common to external. Can be removed from the repository, the sources are elsewhere. JM From: "E. Choroba" ***@***.***> To: "ufal/TrEd-extensions" ***@***.***> Cc: "Subscribed" ***@***.***> Sent: Thursday, 10 October, 2024 13:20:13 Subject: [ufal/TrEd-extensions] discourse extension has a wrong dependency (Issue #3) At [ https://ufal.mff.cuni.cz/tred/extensions | https://ufal.mff.cuni.cz/tred/extensions ] , discourse depends on nondeprel_common , but it's location is incorrectly referred to as external (should be core ). In the repository, the path is correct, but the version is 1.149, while the one ufal is 1.157. Where is it coming from and could it be fixed there (and probably removed from here)? — Reply to this email directly, [ #3 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AEGAYYIEUOHTGYLLRWNLNQLZ2ZPG3AVCNFSM6AAAAABPWRQLYSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TQNJTGY2DONY | unsubscribe ] . You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[jmirovsky]

The bridging, discourse and nondeprel_common extensions have been moved to external. Can be removed from TrEd repository. JM From: "E. Choroba" ***@***.***> To: "ufal/TrEd-extensions" ***@***.***> Cc: "Subscribed" ***@***.***> Sent: Thursday, 10 October, 2024 13:20:13 Subject: [ufal/TrEd-extensions] discourse extension has a wrong dependency (Issue #3) At [ https://ufal.mff.cuni.cz/tred/extensions | https://ufal.mff.cuni.cz/tred/extensions ] , discourse depends on nondeprel_common , but it's location is incorrectly referred to as external (should be core ). In the repository, the path is correct, but the version is 1.149, while the one ufal is 1.157. Where is it coming from and could it be fixed there (and probably removed from here)? — Reply to this email directly, [ #3 | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AEGAYYIEUOHTGYLLRWNLNQLZ2ZPG3AVCNFSM6AAAAABPWRQLYSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TQNJTGY2DONY | unsubscribe ] . You are receiving this because you are subscribed to this thread. Message ID: ***@***.***>

[matyaskopp]

If you want to remove it, then I suggest preserving the folder in the same way as it is done in the pmltq extension https://github.com/ufal/TrEd-extensions/tree/main/pmltq
I am using an empty .gitkeep file there.

[jmirovsky]

I do not care what happens to it. I have always had these extensions in my own repository and I did not put them i the TrEd repository. From: "Matyáš Kopp" ***@***.***> To: "ufal" ***@***.***> Cc: "Jiri Mirovsky" ***@***.***>, "Comment" ***@***.***> Sent: Thursday, 10 October, 2024 14:17:05 Subject: Re: [ufal/TrEd-extensions] discourse extension has a wrong dependency (Issue #3) If you want to remove it, then I suggest preserving the folder in the same way as it is done in the pmltq extension [ https://github.com/ufal/TrEd-extensions/tree/main/pmltq | https://github.com/ufal/TrEd-extensions/tree/main/pmltq ] I am using an empty .gitkeep file there. — Reply to this email directly, [ #3 (comment) | view it on GitHub ] , or [ https://github.com/notifications/unsubscribe-auth/AEGAYYOKSOCTE4LEQ6EQOITZ2ZV4DAVCNFSM6AAAAABPWRQLYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBUHEZTENZUGM | unsubscribe ] . You are receiving this because you commented. Message ID: ***@***.***>

[choroba]

Which brings me into an idea I've had recently. What about extending the package.xml with a new field which would say what repository the external extension comes from? So for example the new umr extension will have

<vc href="github.com:ufal/UMR/tred_extension/umr" path="tred_extension/umr" />

or something similar.

The problem is we need to extend the schema for the package.xml, which means old TrEd will not work with the new xml's. So we need at least a way to release a new TrEd 😉