All pastes #122794 Raw Edit

Someone

public text v1 · immutable
·published 2006-08-08 22:40 UTC
rendered paste body
01:51 < tseng> meebey_: ping
01:51 < tseng> meebey_: are you working on the gtk# split?
01:52 < meebey_> tseng: did they release the new splitted version?
01:53 < tseng> yes
01:53 < meebey_> url?
01:54 < tseng> moment
01:57 < tseng> sigh
01:57 < tseng> the ubuntu gnome guy bugged me about it and now he wont answer
01:57 < meebey_> hm
01:58 < tseng> i dont see it on this gnome mirror yet
01:58 < meebey_> I will take care as soon as I find a release tarball :) I give that top priority
01:58 < tseng> thanks :D
01:58 < meebey_> its a very important step for us
01:58 < tseng> yep
01:58 < dmoonfire> "splitted version"?
01:58 < tseng> dmoonfire: gnome-sharp split from gtk-sharp
01:59 < tseng> gnome-sharp is not guaranteed abi stable
01:59 < meebey_> required by gnome policies
01:59 < tseng> in the underlying libs
01:59 < dmoonfire> Ah.
01:59 < meebey_> desktop vs plattform libs
01:59 < dmoonfire> Sounds like more work, but cool.
01:59 < tseng> not much
01:59 < tseng> we already split it all up by assembly
01:59 < meebey_> yeah, just need to split source package
02:00 < meebey_> and see if they moved some other thing too
02:00 < meebey_> binary wise, it should be all the same
02:00 < tseng> doubt it
02:00 < dmoonfire> Bah, I need to finish the clipolicy example.
02:00 < dmoonfire> I hate vacations (starts tomorow).
02:00 < tseng> thats funny
02:01 < meebey_> :)
02:01 < dmoonfire> My boss ALWAYS insists on 15 hour days right before a vacation.
02:01 < meebey_> btw is dh_createclipolicy better than dh_makeclipolicy?
02:01 < meebey_> or maybe gen
02:01 < meebey_> I am not sure what the script does so, I cant say which fits betters
02:01 < meebey_> -s
02:02 < meebey_> there is dh_makeshlibs and dh_gencontrol as reference
02:02 < dmoonfire> It takes a .clipolicies file and generates one or more policy dll's (and sets up the autoinstalls) for every version.
02:02 < dmoonfire> It also handles ABI breakage on later versions, and properly policy'ing them.
02:02 < meebey_> I hope not too much magic :-P
02:03 < meebey_> else nobody will understand what it does
02:03 < dmoonfire> I also got it to support installing multiple DLL's at the same time, and figure out the "best" case. :)
02:03 < meebey_> so it generates XML + compiles XML + installs into GAC (late)?
02:03 < dmoonfire> Yep.
02:03 < meebey_> sounds cool
02:04 < meebey_> hm
02:04 < meebey_> wouldnt it be better if you reuse dh_installcligac?
02:04 < meebey_> or do you do that?
02:04 < dmoonfire> And it generates policies so you can say: 2.0.0.0 handles 1.0.0.0-1.2.0.0, 2.1.0.0 handles 2.0.1.0, etc.
02:04 < dmoonfire> I reuse the dh_installcligac scripts.
02:05 < tseng> http://ftp.acc.umu.se/pub/GNOME/sources/gtk-sharp/
02:05 < meebey_> ic
02:05 < meebey_> tseng: thanks
02:05 < tseng> http://ftp.acc.umu.se/pub/GNOME/sources/gnome-sharp/
02:05 < dmoonfire> I needed a bit more extra functionality to handle the uninstall/selection stuff.
02:05 < meebey_> ic
02:05 < tseng> http://ftp.gnome.org/pub/GNOME/LATEST.xml
02:05 < tseng> this is nice
02:06 < meebey_> 2.10 is the comming gtk+?
02:07 < tseng> yep.
02:07 < tseng> wel
02:07 < tseng> l
02:07 < tseng> gtk+ 2.10.x is already released
02:07 < tseng> but gtk# 2.9 means its still in development
02:07 < tseng> and will be gtk# 2.10
02:07 < tseng> not perfect, but better than gtk# 1.0.10
02:07 < tseng> much better :)
02:08 < PChot> meebey_: ar u in a good mood to make experimental debs?
02:08 < meebey_> :)
02:08 < meebey_> PChot: nope
02:08 < tseng> we told you how to make your own
02:09 < meebey_> PChot: apt-get source mono; download 1.1.16; copy the debian/ directory into mono-1.1.16; add new entry in debian/changelog; run dpkg-buildpackage
                 -us -uw -rfakeroot in mono-1.1.16
02:09 < meebey_> PChot: done
02:09 < PChot> sorry, don't have enought time at the moment :(
02:09 < dmoonfire> Now, the only thing I had a problem with the .policyassemblies file. I have a current example at: http://pastebin.ca/122167
02:10 < dmoonfire> I needed a fair amount of information when I actually got to generating it, hence the file format.
02:12 < meebey_> hm ic
02:12 < dmoonfire> On the other hand, it will allow historical generation of the policy files.
02:13 < dmoonfire> So, you just have to append/update as new versions come out and the new policy file will automatically handle it.
02:14 < tseng> PChot: if you don't have time to do your own work after walked through it twice
02:14 < tseng> PChot: please don't ask for our time.
02:17 < meebey_> dmoonfire: whats the priority for?
02:18 < dmoonfire> Highest priority is used, if available.
02:18 < dmoonfire> Basically, every package generates a set of policy files (with the priority), and the highest is late-installed.
02:19 < dmoonfire> That way, if you install an older version (for some reason), the policy stuff will still work properly.
02:19 < meebey_> so the maintainer needs to keep track of the prios in his packages
02:19 < dmoonfire> When you uninstall a package, it removes its policy files and resets the policy  to the next highest.
02:20 < dmoonfire> You just need to increment it very time you change it, that should handle it. I couldn't find a cleaner approach.
02:20 < dmoonfire> Well, I could, but I don't think PRIORITY=`wc -l changelog` was a good approach. :)
02:21 < meebey_> increment per package you mean
02:21 < dmoonfire> You only have to increment when you change the policyassemblies file.
02:21 < dmoonfire> And for that specific file.
02:22 < meebey_> hm
02:22 < meebey_> sounds error prone then
02:22 < dmoonfire> I didn't know if the "wc" was acceptable (which would cover 99% of the cases)
02:22 < meebey_> its not acceptable :)
02:22 < tseng> its pretty crap
02:22 < dmoonfire> True, but I need a better approach for automatically incrementing it.
02:23 < meebey_> but bumping the priority on each change sounds unneeded
02:23 < dmoonfire> Well, I use it to figure out which set of policy files are the "most current"
02:23 < dmoonfire> And the normal A.B.C version scheme wasn't consistent enough to use.
02:24 < dmoonfire> Either for the DLL files or the Debian package (which can be 1:1.2.3pre4 or even more complicated)
02:24 < tseng> dpkg --compare-versions ?
02:24 < meebey_> yeah
02:24 < tseng> and use the debian version #
02:24 < meebey_> that sounds more sane
02:25 < meebey_> that will not work across debian packages, will it?
02:25 < tseng> why across?
02:25 < dmoonfire> And it won't handle splitting packages midstream.
02:25 < tseng> yes, gtk-sharp
02:25 < meebey_> tseng: because the policy are also for files of other packages
02:26 < meebey_> its the crappy scenario
02:26 < meebey_> IMHO we need to write some expected scenarios down
02:27 < meebey_> if nobody is able to understand the issue in the first place, nobody can use the script correctly :)
02:27 < dmoonfire> True, plus examples never hurt.
02:27 < dmoonfire> If I get the scenarios, I can show you how I would have written the file.
02:27 < meebey_> thats the examples you talked about, right? :)
02:27 < dmoonfire> And maybe someone can find improvements.
02:28 < meebey_> yeah
02:28 < meebey_> take a real-life example please :-P
02:28 < dmoonfire> Yeah, if you give scenarios, I'll give examples of how to handle them (or fix the code to make sure it can handle them). :)
02:28  * dmoonfire blinks.
02:28 < dmoonfire> I have no real-life examples at the moment, except nunit (I think).
02:29 < meebey_> nunit sounds good
02:29 < dmoonfire> Okay, I'll try to come up with that one. I have an MfGames.Utility version that would also work.
02:29 < dmoonfire> And log4net (sort of)
02:29 < dmoonfire> But, its going to be a week or so (I'm going to a convention tomorrow).
02:29 < meebey_> more examples, better :)
02:29 < meebey_> np
02:30 < dmoonfire> You want them in the .sgml or just emailed until it gets stablized?
02:30 < meebey_> we need a good implementation, else we shoot in our feet :)
02:30 < meebey_> dont we have a wiki?
02:30 < meebey_> wiki.debian.net
02:30 < meebey_> thats easier to collaborate
02:31 < dmoonfire> Okay, I was thinking mailing list, but wiki works too.
02:31 < meebey_> what I dont like about mailing lists is you dont have a latest-version :)
02:31 < meebey_> you have one proposal and many comments :)
02:31 < dmoonfire> Picky, picky.
02:32 < meebey_> hehe
02:32 < dmoonfire> Okay, I'll try to come up with a couple of examples in a week or so. Along with source files to produce it.