Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is there a NuGet package for this available? #28

Closed
matthid opened this issue May 1, 2018 · 8 comments · May be fixed by #32
Closed

Is there a NuGet package for this available? #28

matthid opened this issue May 1, 2018 · 8 comments · May be fixed by #32

Comments

@matthid
Copy link
Member

matthid commented May 1, 2018

What I found is https://www.nuget.org/packages/Xake/1.0.3-alpha5 Is there more or is everything part of this package?
I would like to add this to the fake documentation as an alternative to the targets-syntax. Is this something you would be interested in?
Have you ever tried to use this in combination with the fake 5 runner?

@matthid
Copy link
Member Author

matthid commented May 1, 2018

Oh I didn't realize you are already on it (briefly mentioned in fsprojects/FAKE#1888).
Feel free to send PRs to fake docs if you are ready :)

@OlegZee
Copy link
Collaborator

OlegZee commented May 2, 2018

@matthid, I would be glad this project to be part of FAKE 5 and currently working on migration everything to netcore. What do you think if we give it a different name, such as Fake.Recipes or Fake.Scripts?

Have you look over the docs? There're a bunch of cool features such as incremental builds, estimate time prediction and progress indicator. It's similar to google's Bezel and originally it was an attempt to copycat Shake.

It currently works with FAKE5 and I just pushed the netcore-bootstrap example.

@matthid
Copy link
Member Author

matthid commented May 3, 2018

Ok to give you a rough roadmap: After the fake 5 release the next logical step would be to extract some modules into their own repository. Therefore it doesn't make a lot of sense to make something (that is already living on it's own) part of the fake repository now until we are at some later stage.

From a users perspective it doesn't make a lot of difference where the code lives as the integration is easy (just add the module). Like I said - I welcome update to the docs (which should make it seamless and not noticeable to users where the actual code lives).

If you want to rename your project because of this integration that would be up to you but not required from my point of view. (though it would obviously match the fake naming scheme)

@OlegZee
Copy link
Collaborator

OlegZee commented May 4, 2018

@matthid, thanks, good!

@matthid
Copy link
Member Author

matthid commented May 5, 2018

To reword/clarify a bit (edited some errors above): It doesn't make a lot of sense to add stuff which already is perfectly split into it's own repository. But if the integration Fake-Xake happens to break in the future I'm perfectly open to adding it to the fake repository.

I guess for now we would have something like a new "folder" in the modules menu:

  • Modules
    • Build DSL
      • Fake.Core.Target
      • Xake

Closing this for now as I feel like we have similar ideas going forward. Looking forward to this :)

@matthid matthid closed this as completed May 5, 2018
@OlegZee
Copy link
Collaborator

OlegZee commented May 16, 2018

@matthid I completed migration to netcore/FAKE 5, extracted .NET specific tasks to a separate assembly, updated docs and so on.

Could you please add a module reference to FAKE 5 docs and RT https://twitter.com/olegzeee/status/996801367514677248?

@matthid
Copy link
Member Author

matthid commented May 16, 2018

Maybe Like this? Feel free to send updates - I have no idea how to integrate as we currently kind of used the "module-category" (basically the namespace). I'm open for ideas :)

@OlegZee
Copy link
Collaborator

OlegZee commented May 17, 2018

@matthid that is fine now, thank you very much!

@OlegZee OlegZee linked a pull request Feb 22, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants