On Wed, May 29, 2019 at 1:12 AM Rainer Müller <rai...@macports.org> wrote:
> On 28.05.19 09:11, Rajdeep Bharati wrote: > > I am packaging buildbot 2.x as a port. However, a key part of buildbot 2 > > is the web interface, buildbot-www, which uses many javascript > > dependencies (those aren't available as MacPorts packages yet). Please > > find the attached image which shows the dependencies. > > > > Screenshot 2019-05-28 at 11.36.55 AM.png > > < > https://drive.google.com/file/d/1CnjcmMvd4fsXtJqhjrTRGVC0Rfn2s9gW/view?usp=drive_web > > > > > > What would be the right way to package this? Would it be a python port? > > Would it be better to package all of the above JS libraries? > > Out of curiosity, where does this screenshot come from? > > It's present in the UI: https://nine.buildbot.net/#/about > To me it looks like all of these (minified) JavaScript libraries and > also FontAwesome are already included in the release tarball. You do not > need to create ports for these, the software will use the included copies. > > I didn't understand how it would use the included copies. > $ tar xf buildbot-www-2.3.1.tar.gz > $ $ tree buildbot-www-2.3.1/buildbot_www/static > buildbot-www-2.3.1/buildbot_www/static/ > ├── d3.min.js > ├── fonts > │ ├── FontAwesome.otf > │ ├── fontawesome-webfont.eot > │ ├── fontawesome-webfont.svg > │ ├── fontawesome-webfont.ttf > │ └── fontawesome-webfont.woff > ├── img > │ ├── favicon.ico > │ ├── icon.png > │ ├── icon.svg > │ ├── icon16.svg > │ └── nobody.png > ├── index.html > ├── scripts.js > ├── styles.css > └── tests.js > > Rainer > Rajdeep
