Re: Ripping out GLib bindings, depending on GLib

[Andreas Rottmann]

Rob Browning <address@hidden> writes:

> Andreas Rottmann <address@hidden> writes:
>
>>>     rsync --rsh=ssh distribution.tar.gz \
>>>       address@hidden:/upload/g-wrapg-wrap
>>>     sftp -1 address@hidden:/g-wrap
>>>     scp distribution.tar.gz address@hidden:/upload/g-wrapg-wrap
>>>
>> Well, I still wonder if you can upload entire directory trees...
>
> Not sure, actually, but the only reason I thought about the idea in
> the first place is because someone else mentioned offhand something to
> the effect that you could host arch stuff from savannah that way.
>
>>> and that if/when I'm ready to make it read-write, I can do that via
>>> various methods, including tla-pqm (which I'm not familar with
>>> yet)?
>>>
>> I think the best way would be, if we go "centralized", to set up a
>> new archive (named something like address@hidden) and
>> then tag the branches in there from your current archive (plus
>> cachrev them in the new archive for efficiency). Rythmbox is setup
>> this way, have a look at [1]; the public archive is branched from
>> Walters' private one.
>>
> Hmm.  OK, I'll have to check that out.  How would day-to-day
> development work when using that approach?
>
According to the tla-pqm docs:

,----
| You create the distinguished archive to be managed by the patch queue
|  manager. Then, every developer branches off of it. When a developer
|  has reached a milestone and wants to sync up the main tree with their
|  archive, they submit a merge request.
`----

You would naturally not need to branch off, since the central archive
would be a branch of your archive.

-- 
Andreas Rottmann         | address@hidden      | address@hidden | address@hidden
http://yi.org/rotty      | GnuPG Key: http://yi.org/rotty/gpg.asc
Fingerprint              | DFB4 4EB4 78A4 5EEE 6219  F228 F92F CFC5 01FD 5B62

Packages should build-depend on what they should build-depend.