I’ll have to think more about it and have a play…

 

In terms of regular koha-testing-docker dev/test usage, I think that you’d only 
need to build once in a while (unless you’re changing ERM code)? So I’m not too 
worried about this.

 

But how does the yarn build factor into building Koha packages? Do we need to 
add the yarn build to the debian/rules file? Or would we change 
“debian/build-git-snapshot” to unpack the “git archive”, do the yarn build, and 
then re-package and pass to pdebuild?

 

David Cook

Senior Software Engineer

Prosentient Systems

Suite 7.03

6a Glen St

Milsons Point NSW 2061

Australia

 

Office: 02 9212 0899

Online: 02 8005 0595

 

From: Koha-devel <koha-devel-boun...@lists.koha-community.org> On Behalf Of 
Tomas Cohen Arazi
Sent: Thursday, 10 November 2022 2:54 AM
To: koha-devel <koha-devel@lists.koha-community.org>
Subject: [Koha-devel] ERM - workflow change

 

Hi all, we pushed ERM but didn't communicate some decisions made:

 

- For running the ERM component (and in the future any other Vue-driven thing) 
a build step needs to happen. Either:

 

$ yarn build_js

 

or (the dev-oriented version):

 

$ yarn watch_js

 

- We could've gone 'the SCSS' way, in which the RM(aint) compiles the thing and 
pushes to Git along with the changes. But we decided it would have an impact on 
the size of the repository pretty fast. So for now, the decision is we will do 
it at release time. This is also common practice on Vue projects.

 

- We could add the build as part of the 'reset_all' command KTD users are 
familiar with. TBD

 

- Yes, now that running Koha requires a build step, we could just add SCSS 
there, that's to be discussed early next cycle.

 

- We need a way to pre-bundle all the dependencies in KTD, so people can fire 
up KTD while being offline. Agustín is wrapping up a proposal for this. TBD


 

Please share your thoughts, and sorry for not communicating this earlier.

 

-- 

Tomás Cohen Arazi

Theke Solutions (http://theke.io <http://theke.io/> )
✆ +54 9351 3513384
GPG: B2F3C15F

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : https://www.koha-community.org/
git : https://git.koha-community.org/
bugs : https://bugs.koha-community.org/

Reply via email to