Hi,
On Thu, Nov 7, 2013 at 3:39 PM, Norbert Hartl <norb...@hartl.name> wrote: > Btw. how is the ConfigurationOfPetitParser supposed to work? I loaded the > one from the moose repo. Looking at it I need to use at least 1.6 because > earlier versions have still Lukas’ repositories configured. But if I load > 1.6 and try to use Versionner it shows me that I have 1.8-snapshot loaded. > Is this a problem of versionner because of the use of snapshotocello it > can’t find version numbers in the version methods? So even if I’m willing > to use the 1.8-snapshot version I can’t because I want to load only the > core and not the rest of the universe but the groups are missing in > 1.8-snapshot while being there in 1.7-snapshot. > > I would be glad if someone could shed some light how this should work and > why it needs all the added complexity. > There is no light other than what you described above. If you want to generate a manual version, you can do that at any time. The current Moose process is to use Snapshotcello and we are unlikely to move away from it in the near future. Diego has a proposal for extending Snapshotcello to preserve the configuration structure, but until that is finished, we live with what we have. Of course, contributions are more than welcome. > My advize would be to separate metacello configurations for the different > uses of it. I do the same with my own projects because it causes less > trouble. A ConfigurationOfPetitParser and a separate > ConfigurationOfPetitGui that introduces dependencies to glamour et al. > would save some headaches for people that are only interested in > PetitParser. > Thanks for the advice. That is precisely what I meant about people wanting to commit to do things :). There are many ways to make things flexible, but they all come with associated effort. If someone offers to put the effort into it, it would be great. Cheers, Doru > Norbert > > > Am 07.11.2013 um 13:13 schrieb Norbert Hartl <norb...@hartl.name>: > > > > Am 07.11.2013 um 12:12 schrieb Tudor Girba <tu...@tudorgirba.com>: > > Hi, > > I think you missed my point. I know I can technically load the code from > multiple places :). > > I know you know. I couldn't miss the point because for me there is none :) > > For Moose, PetitParser is an important component that is being developed > by the team. Up to now, we did that, hence it made perfect sense to have it > in the Moose team repository and in our responsibility. > > Agreed. I have just a different view. I'm using petit parser since 2 1/2 > years and to me it never made any sense moving it into moose :) > > Moving is no problem, as long as we ensure that others actually do > something, and that the development does not go in strange directions > (which I agree it is unlikely). As I said, it would be great to see > PetitParser in the Pharo image and be used by Opal. > > > Ok, no need to argue. Nothing is carved in stone. I just like to say that > I would prefer petit parser breaking loose from moose. > > Norbert > > > > > On Thu, Nov 7, 2013 at 11:58 AM, Norbert Hartl <norb...@hartl.name> wrote: > >> >> Am 07.11.2013 um 11:46 schrieb Tudor Girba <tu...@tudorgirba.com>: >> >> Hi, >> >> It is in the Moose repository because Moose was essentially the first >> larger user (besides Helvetia) since its inception (more than 3 years now), >> and because the development of PetitParser was taken care of by the Moose >> team. >> >> Being a user of a software is not a good reason to tie it to it. Ask Stef >> ;) It is nice if the moose team took (and takes) care for it. But you can >> take care in another repository as well. I think petit parser is an >> important and standalone package that has nothing to do with moose. Putting >> this inside another project just weakens the included project. >> >> If others want to contribute (and even integrate into Pharo), it would be >> great and then we should move it. But, moving should come with commitment. >> This is an important piece in Moose and we need it to stay working and >> compatible with Moose requirements. >> >> That is what metacello is for. Refer to the versions you need and you are >> off the races. As you are one of those who maintains it you are even in the >> position to _not_ integrate every other change. So if the write restriction >> to petit parser (being in the moose repo) is the solution we should talk. >> >> Norbert >> >> Cheers, >> Doru >> >> >> >> >> On Thu, Nov 7, 2013 at 11:19 AM, Norbert Hartl <norb...@hartl.name>wrote: >> >>> >>> Am 07.11.2013 um 11:07 schrieb Stephan Eggermont <step...@stack.nl>: >>> >>> > The official repository of PetitParser is >>> > Moose/PetitParser >>> > on smalltalkhub >>> > >>> thanks. >>> >>> > >>> http://forum.world.st/moving-petitparser-to-smalltalkhub-td4671840.html >>> > >>> Well, this is not a good place IMHO. A more independent but official >>> repo would be nice. >>> >>> Norbert >>> >>> >>> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > > -- www.tudorgirba.com "Every thing has its own flow"
