<robertodecurnex>
you dont need EVERY file of the repo to be included on the gem
<pipework>
robertodecurnex: Why not?
<robertodecurnex>
that's another ugly practice
<pipework>
Typically, I do want everything. What should I not want?
<pipework>
Even tests.
<slash_nick>
pipework: I dunno, readme, examples
<robertodecurnex>
ty!
<pipework>
slash_nick: You wouldn't want to include documentation?
<slash_nick>
not in the .gem that's built by running "gem build blah"
<slash_nick>
not necessarily
<robertodecurnex>
there area A LOT of repos holding even binaries, useless for the final user
<pipework>
Why not? When you generate rdocs from it, it might beneft from it.
<pipework>
robertodecurnex: Which are using precompiled binaries that aren't meant for the end user?
<robertodecurnex>
RDOC MUST be generated locally
<pipework>
So?
<robertodecurnex>
user has the freedom of install docs or not, and define the format
<pipework>
You need the documentation source to generate it.
<robertodecurnex>
the DOC is part of teh code
<slash_nick>
pipework: I'm thinking of a mygem/samples/ directory with a ton of images
<pipework>
If I write a readme and examples, I want the source of the documentation shipped.
<robertodecurnex>
let's see....
<pipework>
slash_nick: I could see it as an opportunity to include it in the doc source, but arguably that they might not want the gem to ship it too.
<pipework>
robertodecurnex: You're welcome to generate with whatever you want, or to not. But I will write my documentation strings how I want and it's up to you to deal with whatever they output when you run it through your documentation generator.
<robertodecurnex>
sure it is
<robertodecurnex>
you can include whatever you want
<slash_nick>
robertodecurnex: it's not a big deal. if a dev is big-boy enough to write a gem, he's also capable of specifying which files will be used in building the gem
<robertodecurnex>
but right now everyone is including everything
<robertodecurnex>
slash_nick: lot of them are not
<slash_nick>
robertodecurnex: post issues
<pipework>
robertodecurnex: I'd think that if there's things I don't want in the gem, I'd either whitelist or blacklist them, but most always I want everything in my gems.
cwebber has joined #bundler
<pipework>
I don't want to get into the practice of #{gem}, #{gem}-docs, #{gem}-examples, #{gem}-tests
<robertodecurnex>
Anyway, there are two problems here.
<robertodecurnex>
1st everythign is included, I can live with it (maybe :p)
axl_ has quit [Quit: axl_]
<robertodecurnex>
2nd now building a gem requires git and the repo
<robertodecurnex>
that's way too mcuh
<slash_nick>
robertodecurnex: in no way does building a gem require git
<robertodecurnex>
yes it is, have you ever shipped productive code via GEMS ?
<robertodecurnex>
to a VPS, not heroku
<slash_nick>
robertodecurnex: not sure what you're asking
<pipework>
robertodecurnex: Well, only if you want to modify the gem but really don't want to modify the gemspec.
<slash_nick>
notice `git ls-files` is in backticks... you could just as easily `ls` the files
<robertodecurnex>
ls is much better, but it will add the git meta files
<robertodecurnex>
and its OS dependent
<slash_nick>
robertodecurnex: okay so `ls something | grep -v "exclude_this_string"`
<robertodecurnex>
using RUBY would be the safer path
<slash_nick>
robertodecurnex: so use that, what's the problem?
<robertodecurnex>
I not even use "bundler gem"
<robertodecurnex>
but every gem I install is corrupted by the git ls-files
<slash_nick>
robertodecurnex: so make issues on those gems github repos
<robertodecurnex>
and most of the developer on my company are used to that
<robertodecurnex>
... it's budler, it's supposed to be an example of how things should be done
robbyoconnor has quit [Read error: Operation timed out]
<slash_nick>
robertodecurnex: i agree the template produced should be a good example.
<slash_nick>
robertodecurnex: don't you think the ruby code to list those files while excluding those items you'd like excluded would be a little... messy?
<slash_nick>
git-ls-files takes into account the .gitignore
<robertodecurnex>
Yes, and the .git directories
werdnativ has quit [Quit: werdnativ]
<robertodecurnex>
That's the adventage of git ls-files, and the reason why it's probably still thre
<slash_nick>
Right, those too... it's clean, it's OS agnostic, you can include/exclude whichever files you want
<robertodecurnex>
but the cost seems to be too much, at least for me
<slash_nick>
robertodecurnex: you're not locked into it... you can, for your own projects, list the files however you want. for the gems you're installing, you can create issues and pull requests to improve your situation
werdnativ has joined #bundler
<slash_nick>
robertodecurnex: the pull requests might just change the .gitignore
<robertodecurnex>
I'm living with it. It's just that newcomers (and even you) use it without thinking about the cost of having GIT as a dependency.
<robertodecurnex>
It's actually not a bundler thing but a ruby thing
<robertodecurnex>
Most of you are used to use SO files here and thre
<slash_nick>
robertodecurnex: again, git is in no way a dependency
<slash_nick>
SO?
<robertodecurnex>
.SO files, system libraries
<slash_nick>
And that hurts you because windows?
<robertodecurnex>
no, because you need to install lot of packages on your servers/workers
<robertodecurnex>
(even in your machine, but that's not really the problem)
<slash_nick>
robertodecurnex: i'm not sure we're the right audience for this
<robertodecurnex>
you are bundler -> bundler introduces the git ls-files approach to devs -> you are the audience
<slash_nick>
robertodecurnex: I'll back out of this conversation now...
<robertodecurnex>
Yea, I was just looking for quick feedback
<robertodecurnex>
There are better places to discuss this with details
<robertodecurnex>
Just checking if there was a strong argument to do it in that way.
<robertodecurnex>
slash_nick: I appreciate your thougths. Sorry if I got aggressive on my nerd-rage :P
<slash_nick>
robertodecurnex: there is, we went over the reasoning together.
<robertodecurnex>
pipework: same 4 u
<pipework>
robertodecurnex: Passionate people are the ones I prefer to talk with.
<pipework>
I'll have to catch up in a bit.
cha1tanya has quit [Ping timeout: 265 seconds]
robertodecurnex has quit [Ping timeout: 245 seconds]
werdnativ has quit [Quit: werdnativ]
digitalvapor has quit [Ping timeout: 265 seconds]
samphippen has joined #bundler
werdnativ has joined #bundler
werdnativ has quit [Quit: werdnativ]
havenwood has joined #bundler
x1337807x has quit [Ping timeout: 264 seconds]
x1337807_ has joined #bundler
Olipro has quit [Ping timeout: 246 seconds]
x1337807_ has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
Olipro has joined #bundler
woollyams has joined #bundler
woollyams has quit [Ping timeout: 252 seconds]
samphippen has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
samphippen has joined #bundler
samphippen has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
havenwood has quit [Remote host closed the connection]