Kranc should output its directory and branch when it runs

Create issue
Issue #698 open
Erik Schnetter created an issue

Kranc should output its directory and branch when it runs. This should go to the screen, and probably also to the generated thorn's README or a small source file. This may help prevent surprises if people accidentally run the wrong version.


Comments (6)

  1. Frank Löffler
    • changed status to open
    • changed component to Kranc
    • removed comment

    We should keep this issue open until it is fixed. Other people might want to report the same otherwise, and only look here.

  2. Ian Hinder
    • removed comment

    By that logic, you would create tickets here for all the current issues in the Kranc issue tracker. I see that someone has created a TRAC component for Kranc. This confuses things, and people will not be aware of the Kranc issue tracker. I think it is better to have a link on the main TRAC page to the Kranc issues page so that if someone wants to look at Kranc issues, they can.

  3. Frank Löffler
    • removed comment

    I agree that this duplication isn't ideal. My idea was to follow the mechanism also used for distributions, where you often have an open ticket for, let's say, a package in Debian, and if this is an upstream issue it is also opened there - and this mentioned in both. Once it is closed upstream the corresponding ticket can be closed in the distribution as well - after it has been applied. This is also the case with Kranc. If something is changed in Kranc a couple of thorns might need to be regenerated, and it would be nice to have a component for these Kranc-related issues. This is not the case for this specific ticket, but it reminded me of other Kranc tickets.

    I would not open a ticket here for everything in the Kranc tracker - only for something which actually was reported here.

    However, you are developing Kranc and it is your decision how you would like to deal with Kranc issues.


  4. Ian Hinder
    • removed comment

    I see what you mean, but I think it's a bit too much overhead for us. If something is changed in Kranc that affects ET thorns, we can create tickets for these thorns in the ET trac. To keep things simple and avoid extra work and possibly confusion, I would keep all Kranc issues in the Kranc tracker. We can have a link on the main ET TRAC page pointing to the Kranc tracker, and maybe a message which says this. The Ubuntu/Debian case is different, in that they need to handle their issues separately from upstream, and might have local patches etc. That is not the case here, since the ET does not repackage Kranc, but just includes it directly.

  5. Log in to comment