<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 01/10/2013 22:14, luiz americo
      pereira camara wrote:<br>
    </div>
    <blockquote
cite="mid:CAMa0j63WswuX+sQtnw+zCp8fih7apb5qK1zyKkV6Gcaej==juw@mail.gmail.com"
      type="cite">
      <div dir="ltr"><br>
        <div class="gmail_extra"><br>
          <br>
          <div class="gmail_quote">2013/10/1 luiz americo pereira camara
            <span dir="ltr"><<a moz-do-not-send="true"
                href="mailto:luizmed@oi.com.br" target="_blank">luizmed@oi.com.br</a>></span><br>
            <blockquote class="gmail_quote" style="margin:0px 0px 0px
              0.8ex;border-left:1px solid
              rgb(204,204,204);padding-left:1ex">
              <div dir="ltr"><br>
                <div class="gmail_extra"><br>
                  <br>
                  <div class="gmail_quote">2013/10/1 Martin <span
                      dir="ltr"><<a moz-do-not-send="true"
                        href="mailto:lazarus@mfriebe.de" target="_blank">lazarus@mfriebe.de</a>></span><br>
                    <blockquote class="gmail_quote" style="margin:0px
                      0px 0px 0.8ex;border-left:1px solid
                      rgb(204,204,204);padding-left:1ex">
                      <div>
                        <div class="im">On 01/10/2013 14:14, Martin
                          wrote:<br>
                        </div>
                        <div class="im">
                          <blockquote class="gmail_quote"
                            style="margin:0px 0px 0px
                            0.8ex;border-left:1px solid
                            rgb(204,204,204);padding-left:1ex">
                            <br>
                            I looked at it. But currently, it looks like
                            it may cause problems.<br>
                            <br>
                            Both packages share the same folders, that
                            can lead to conflicts.<br>
                          </blockquote>
                        </div>
                      </div>
                    </blockquote>
                    <div><br>
                      []<br>
                       </div>
                    <div class="im">
                      <blockquote class="gmail_quote" style="margin:0px
                        0px 0px 0.8ex;border-left:1px solid
                        rgb(204,204,204);padding-left:1ex">
                        <div>
                          <blockquote class="gmail_quote"
                            style="margin:0px 0px 0px
                            0.8ex;border-left:1px solid
                            rgb(204,204,204);padding-left:1ex">
                            <br>
                            <br>
                          </blockquote>
                          <br>
                        </div>
                        I have added the fcl package. BUT<br>
                        <br>
                        - The normal package, is kept as it. One package
                        that contains all, and does not need the fcl
                        package (in fact may have issues if both are
                        used / not tested)<br>
                        - The fcl pacage as a separate unit directory.
                        It can be used INSTEAD of the normal package.</blockquote>
                      <div><br>
                      </div>
                    </div>
                    <div>Your <span lang="en"><span>worries are
                          pertinents. I hit this problem sometimes.<br>
                          <br>
                        </span></span></div>
                    <div><span lang="en"><span>I haven't looked at this
                          specific package but the best approach is to
                          create a package that depends only from FCL
                          and create a LCL package that uses the first
                          one. Most of the time, this can be done
                          without sharing source paths without much
                          work.<span class=""><font color="#888888"><br>
                            </font></span></span></span></div>
                    <span class=""></span></div>
                </div>
              </div>
            </blockquote>
            <div><br>
            </div>
            <div>I looked at the commited files and this configuration
              will cause problems when installing both packages. Notice
              that is important to allow the installation of the two
              packages, in the same IDE. In some projects (a desktop)
              may be necessary to use the complete package while in
              others (a web service) only the base package is necessary.<br>
              <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    You do NOT need to install, in order to use in projects.<br>
    <br>
    Install is only needed for editor macros.<br>
    <br>
    <blockquote
cite="mid:CAMa0j63WswuX+sQtnw+zCp8fih7apb5qK1zyKkV6Gcaej==juw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>There are some solutions:<br>
              <br>
            </div>
            <div>- Put source files of each package in separated
              folders. As an example see: <a moz-do-not-send="true"
href="https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fcairo">https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fcairo</a>
              . Each package has it's own folder.<br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    I need to keep files easy to sync with the original GIT. Therefore
    no. (unless it happens in the original too.)<br>
    <br>
    <blockquote
cite="mid:CAMa0j63WswuX+sQtnw+zCp8fih7apb5qK1zyKkV6Gcaej==juw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>
            </div>
            <div><br>
              - Use the same folder for the source  and ensure that all
              files are added to it's corresponding package. As an
              example see: <a moz-do-not-send="true"
href="https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluicomponents">https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluicomponents</a>
              . Failing to setup properly the package may lead to
              problems. Recently i fixed one in <a
                moz-do-not-send="true"
href="https://code.google.com/p/luipack/source/detail?spec=svn1089&r=1079">https://code.google.com/p/luipack/source/detail?spec=svn1089&r=1079</a><br>
              <br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    Same folder for source does not work, the LCL package will find
    fcl-belonging pas files, and use them instead of ppu (even if not
    listed in package)<br>
    <br>
    <blockquote
cite="mid:CAMa0j63WswuX+sQtnw+zCp8fih7apb5qK1zyKkV6Gcaej==juw@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div class="gmail_extra">
          <div class="gmail_quote">
            <div>- Use the same folder for the source but configure a
              different unit output dir. Example <a
                moz-do-not-send="true"
href="https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluidialogs">https://code.google.com/p/luipack/source/browse/#svn%2Ftrunk%2Fluidialogs</a><br>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    See above.<br>
    <br>
  </body>
</html>