If you do whatever git command that pulls from the remote or pushes to the remote, what will happen to files in the linked in directories?

I excluded 3.0.33 from being included in git operations.

TLF is particular but for others, there's still the possibily to use submodules, I don't like it too much but it is possible to use it, I'm currently testing testing one other option, if it works, it could be simplier than submodules.

-Fred

-----Message d'origine----- From: Alex Harui
Sent: Monday, March 18, 2013 4:31 AM
To: dev@flex.apache.org
Subject: Re: [Falcon] building

A question about file links:

If you do whatever git command that pulls from the remote or pushes to the
remote, what will happen to files in the linked in directories?

When we finally get falcon production ready, are we going to link it into
the SDK?  I hope not.  Falcon is also being used for FlexJS.  Now is the
time to practice building from downstream dependencies in different repos.

I expect new repos for BlazeDS and FlexUnit.  It isn't just one link we're
talking about.

-Alex

On 3/17/13 8:24 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:

I didn't about it before and I still have to check it works but because
we've got cygwin, creating a hard link shouldn't be a big deal using ln.

-Fred

-----Message d'origine-----
From: Alex Harui
Sent: Monday, March 18, 2013 4:08 AM
To: dev@flex.apache.org
Subject: Re: [Falcon] building

Sometime soon, unless someone else wants to do it, I will rework the build
scripts for SDK to pull stuff from TLF without using file links or
submodules.  I think it is the best way.


On 3/17/13 9:17 AM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote:

Jose,

We could decide to add TLF as submodule but we Œll have to change the build files in order to tell them to go down of 1 level to pick up the textLayout sub directory as source, in more, at the moment, this directory is picked up
from the TLF version, all in all, that would be possible but not with our
current build scripts.

The other drawback with submodules is ..., well, read that [1]

-Fred

[1] http://git-scm.com/book/en/Git-Tools-Submodules#Issues-with-Submodules
<http://git-scm.com/book/en/Git-Tools-Submodules#Issues-with-Submodules>
From: Jose Barragan <mailto:jose.barra...@codeoscopic.com>
Sent: Sunday, March 17, 2013 5:00 PM
To: dev@flex.apache.org
Subject: Re: [Falcon] building

I'm not sure, if I'm still in error, but... Why isn't valid something like
that!?


--
Jose Barragan
Software Architect Chief
Codeoscopic Madrid
C/. Infanta Mercedes, 92.
Planta 5.  505.
28020 Madrid.
Tel.: +34 912 94 80 80

On Mar 17, 2013, at 4:27 PM, Frédéric THOMAS <webdoubl...@hotmail.com>
wrote:

Hi Jose,

We can't, the submodule feature takes  a entire repo, not a sub directory
inside a  repo.

-Fred

-----Message d'origine----- From: Jose  Barragan
Sent: Sunday, March 17, 2013 4:25 PM
To: dev@flex.apache.org
Subject: Re:  [Falcon] building

Ops... sorry for sintax :P

Would not it be better, add the TLF repository as a submodule GIT, at that
point the  SDK?
--
Jose Barragan
Software Architect Chief
Codeoscopic  Madrid
C/. Infanta Mercedes, 92.
Planta 5.  505.
28020  Madrid.
Tel.: +34 912 94 80 80

On Mar 17, 2013, at 4:23 PM, Jose Barragan <jose.barra...@codeoscopic.com>
wrote:


Would not it be better, add the TLF repository as a  submodule GIT SDK at
that point?
--
Jose Barragan
Software  Architect Chief
Codeoscopic Madrid
C/. Infanta Mercedes, 92.
Planta  5.  505.
28020 Madrid.
Tel.: +34 912 94 80 80

On Mar 17,  2013, at 4:06 PM, Frédéric THOMAS <webdoubl...@hotmail.com>
wrote:


For TLF, the point is that with svn, we used  svnexternal to link the
TLF/textLayout sub directory to frameworks\projects\textLayout\3.0.33, this
feature doesn't exist with  git, so, at the moment I go by a hard link, on
my windows 7, I use Link  Shell Extension [1]

-Fred

[1] http://schinagl.priv.at/nt/hardlinkshellext/HardLinkShellExt_X64.exe

-----Message  d'origine----- From: Michael Schmalle
Sent: Sunday, March 17, 2013 3:48  PM
To: dev@flex.apache.org
Subject:  [Falcon] building


Hey,

I have managed to build Falcon  after a half ass attempt to build the
sdk, which failed at text layout  or something, don't know the build
went for 45 minutes then died, looks  like it built most.

But for falcon, we still  have;

<property  name="sdk.branch"
value="${compiler}/../../../sdk/branches/develop"/>

I  had to change it to;

<property name="sdk.branch"  value="${compiler}/../../flex-sdk"/>

I have all the repos side  by side, Erik how did you get all this stuff
to build? Did you recreate  the old directory structure?

These build files are way to brittle  for my taste.

Mike

--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui

Reply via email to